Few questions for Stape Store to enrich event data

Hi

I’m trying to use Stape Store to enrich my Facebook events. I have some question regarding this awesome feature.

First of all, thank you for making this feature so easy to use. It’s fantastic!

Questions:

  1. Is there any storage limit in Stape Store?

  2. How long does it usually take for the data to appear in stape store after 1st purchase? Does it take up to 24 hours? I made a test purchase but didn’t see the data right away.

  3. Does each customer create a new document?

  4. If a customer makes another purchase after a document is already created, will the data overwrite the existing document or create a new one?

  5. When I fetch data from Stape Store, does it count as a request and reduce my request limit?
    Because I’ve noticed that requests seem to be made for each user data point like email, phone, first name, last name, etc.

  6. Is the stape store document creation based on the device/browser?
    For example, if a customer makes a purchase from one browser (creating a document) and then makes another purchase from a different browser, will it create two separate documents? In this case, since it’s the same customer but different browsers, can I still fetch and link the data to the same user?

  7. What is the different use case of Stape Store reStore variable and Stape Store Lookup variable since both are extracting data from stape store. To increase event match quality for FB CAPI, should I use Stape Store reStore variable and Stape Store Lookup variable?

Looking forward to your insights!

Best regards,
Monir

Glad you like it :slight_smile:
This is the first version, additions are already in the works to make Stape Store even better :wink:

Is there any storage limit in Stape Store?

Document size should be up to 1 mb, no other restrictions. But requests to the Stape Store are factored in your plan.

How long does it usually take for the data to appear in stape store after 1st purchase? Does it take up to 24 hours? I made a test purchase but didn’t see the data right away.

Stape Store entries happen immediately, make sure your entry tag works as you expect it to.

Does each customer create a new document?

It depends on the method of how you writing to store and what data you use in document name. If document name is new - a new document will be created. If existing - the old one will be overwritten.

  1. If a customer makes another purchase after a document is already created, will the data overwrite the existing document or create a new one?

If you use as document name for example transaction id - then it is a unique field and a new record will be created.

When I fetch data from Stape Store, does it count as a request and reduce my request limit?
Because I’ve noticed that requests seem to be made for each user data point like email, phone, first name, last name, etc.

Yes, any request to the Stape Store is a request that is accounted in your container billing requests.

Is the stape store document creation based on the device/browser?

This is a database, the document name used is the one you specify in the tag/api call if you use api to send data.
Here are more details about Stape Store:

What is the different use case of Stape Store reStore variable and Stape Store Lookup variable since both are extracting data from stape store.

In brief - reStore var can simultaneously fetch data if it is in the database or write it if it is not.
Here are more details about this one:

Example of usage:

1 Like

Thank you soo much for the detailed explanation. Really appreciate it.

1 Like

Hi,

I’m using the Stape reStore variable to store user data and then retrieving it in server GTM using Stape’s Object Property Extractor. I’m passing this data with Meta events like Page View, Add to Cart, View Item, and Begin Checkout to improve Advanced Matching.

After creating user data variables (email, phone, first_name, last_name) with Object Property Extractor template, I’ve added them in the respective event tags under the User Data section of the CAPI template in server GTM.

Would this setup be sufficient, or should I also use the Transformation option to add user data with Meta event tags?

This approach works quite well, but you can also use transformation - it’s however you prefer.

But also note that the Meta server tag has this functionality, which is probably much the same as what you do with the Stape Store:

This will set a cookie with the user’s data and use it with all future events.
So if you store the user ID for Stape Store data in cookies - this feature will cover your needs quite well.

1 Like

Thanks @Alex for your insights! Love this! :blush:

That means if I enable “Event Enhancement” option is it sets a cookie with ALL user data like:
email
phone
first name
last name
city
postal code
region
country
And after first purchase, page view, view item, add to cart and begin checkout will get all these user data as well, right?
If this is the case then I don’t need to use Stape store to improve event match quality for Meta CAPI. It will make my work much more easier. Could you please clear this things? I’ll really appreciate it.

That’s right. It works as follows:

when the tag receives data with user data - it writes this data to the _gtmeec cookie and in future at the next events when there is no user data it will use the data from the cookie.

That is, if for example a user made a purchase with all user data and then moved to the view item event where there is no user data - the same set of user data will be sent along with the event to the view item as it was at purchase.

1 Like

Thank you soo much. Now everything crystal clear. :heart_eyes:

1 Like