Augment Transformation for Objects from Stape Store

I want to optimize my Stape Store Requests Volume.
Need:I need to retrieve data from the Stape Store, including parameters like gbraid, gclid, wbraid, etc.
Current Problem: I am currently pushing multiple requests to the Stape Store.

I retrieve all the data at once from the relevant document.


However, extracting the object and repeatedly looking it up in the Stape Store triggers unnecessary requests.

@Dan you recommended me using Transformations to avoid triggering unnecessary multiple requests.
Can you guide me how to actually do that?

This is my setup


I see it in the modified values but I can’t do anything with that.

I am quite lost since I can’t create any variable from Augemnted Event. To actually feed any Object Property Extractor variable to use the data later in the tags.

Am I missing something here? Thanks in advance.
Tomas
Tomas

Hey @TomKom what seems to be the issues? You’ve created your ‘obj’ augmented event data, this datapoint is now only available for the tags you’ve applied the transformation to. Now use do notation to pick up individual things:

Hi @Dan My issue was that I thought I needed to use the Object Property Extractor variables to pull data from the augmented object. I wasn’t sure how to do that since the transformation doesn’t create any variables.

But now I get it I hope :sweat_smile: – I don’t need the object extractor. All I need to do is create empty event data variables that the augmentation will change.

It works in my sGTM.
I’ve noted that the transformation initiates a Stape request for each tag I want to use. Or is there a workaround to use the augmented data across tags?

Here’s my example: I need the Stape store data for three tags.

My example - I need the stape store data for 3 tags


So, I define it in the Affected Tags section, as shown in the screenshot above.
Then, for each tag, there is an outgoing request to Stape (screenshots – numbers 4, 5, and 6).
and then for each there is an outgoing request to stape (screnshot - number 4,5,6)

Is this normal behavior? Or is there a better way to use the augmented data across tags?

Thanks
Tomas

hey @TomKom in screenshots above are you certain that lookup is only referenced in transformation, and not the tags directly? Also as far as I recall your situation 1 and 2 could be merged into a single request.

Thanks for reply, @Dan
I have only 2 lookup variables (referenced in the step 1 and 2).
the restult from (2) is used in the transformation (3).
and all the other varibles are just event data variables (4)

Or is there a different way to check if I am only referencing the transformation?
Is there a way to use less requests?

Thanks
Tomas

Hi @TomKom

I have exactly the same doubt. I’ve looked into the case a bit but I still haven’t found any method that seems reliable and corrects the problem. I don’t know if it’s a limitation of sGTM. What happens conceptually is that we do not have a way to define the variables equivalent to a trigger, this way, for each event sGTM will incorporate them and as we are talking about variables that use external requests, they generate requests. The curious thing is that if you use a variable that only formats a certain value of a variable that uses external data, we will have a request for each formatting. There is something in the GTM api that is ‘template_cache’ that I don’t know exactly what the function is yet and whether it would work around these cases. After all, what generates several requests are simple formatting tags. I’ve even thought about creating a custom variavle that performs both functions and tries to lock it for a single request. But it leaves a little of my technical capacity and makes me doubt whether it would actually be possible in sGTM. Looking forward to updates on the topic.