How to enrich conversion data with Stape Store / Firestore?

Google Tag Manager Server Container
1

I want to understand how to properly enrich conversion data with Stape Store / Firestore and send it to the Ad Networks. Let’s say I have 3 events in my funnel: PageView, Lead and Purchase.

Let’s say my Lead event has this data:

This data gets stored in Stape Store / Firestore with the Writer Tags, the moment this webhook is received in the server container URL.

Let’s say a Purchase event happens afterwards and the type of GET call to the webhook that I get is this one:

https://track.mydomain.com/purchase?user_id={user-id}&total_amount={total_amount}

And so, by using the {user-id} parameter I want to be able to locate the document / event in Stape Store / Firestore, and create a new webhook to send the data related to the Purchase event.

This new webhook will be similar to the Lead webhook, but with more data, basically, adding transaction data:

How can I properly implement this? When should I use the variables: “Stape Store Lookup” and “Stape Store Restore” (or the Firestore equivalent variables)?

2

@Dan any updates on this one?

3

you answered it yourself here, I assume your user-id here would be the stitching agent, so you need to store data under that user-id key, and upon receiving a webhook use a lookup variable to pull whatever it is you got stored there

4

Ok, so with the “Firestore (Writer)” tag I will write the data of the Lead event to the DB. Then when I receive the webhook for the Purchase event, I will use the “Firestore (Lookup)” variable to search for the record corresponding to the “user-id” in the DB.

But then, once that record is found matching the user-id, how is the process of merging data and resend the webhook with all the data to the server container URL (and therefore to the corresponding Ad Network tags)?

Also, in which situation should I use “Firestore (Restore)” variable?

5

Ok, so with the “Firestore (Writer)” tag I will write the data of the Lead event to the DB. Then when I receive the webhook for the Purchase event, I will use the “Firestore (Lookup)” variable to search for the record corresponding to the “user-id” in the DB.

correct

But then, once that record is found matching the user-id, how is the process of merging data and resend the webhook with all the data to the server container URL (and therefore to the corresponding Ad Network tags)?

you populate whatever tags you want to fire on the webhook with lookup variables that return the data you need

Also, in which situation should I use “Firestore (Restore)” variable?

not in your situation, restore is for dynamically lookig-up and updating data, more here: Building a custom CDP, enriching event data with server GTM - Stape

1 Like
7

I am currently setting this up. I kind of understand how this should work, but I still have some doubts about the setup. Let’s say my webhook GET call looks like this:

https://track.mydomain.com/purchase?session_id={session_id}&total_amount={total_amount}

I am using the “session_id” as the document key to store previous webhook data associated with this session. This is what a Firestore Lookup variable looks like:

lookup
lookup2646×1734 182 KB

How can I tell the system to grab the “session_id” value from the webhook GET query parameter, and use that value to find the Firestore document with its document key, that session_id value?

8

Event Data variable, key is session_id

Data Client will parse both query parameters and json body as Event Data

1 Like
9

Ok, that was the key of the puzzle that I was missing. So I managed to make it work with those instructions.

Now, how can we have a tidy & clean Firestore database? Is there a way to delete “documents” from a “collection” in Firestore once a document has been “used” by a Tag in GTM? Or maybe after X amount of days?

The idea is not to fill up the database with documents that we no longer need it or that they have been already used.

10

GTM APIs do not have a method for document removal.

There is built-in TTL policy in Firestore, but that works timestamp in Firebase SDK format, which you also can’t generate from under sGTM.

Bottom line is there’s no proper way to remove records the way you’d expect.