curious why you have 102 variables for setup of just purchase event? that’s likely your main culprit for the container size.
as to size in general - that’s a question for Google, can’t help you there.
Here’s the breakdown of the 106 variables:
- 45 Webhook related variables
- 8 Twitter variables (pixel & credentials storage)
- 5 TikTok variables (pixel & credentials storage)
- 4 Snapchat variables (pixel & credentials storage)
- 7 Reddit variables (pixel & credentials storage)
- 8 Microsoft variables (pixel & credentials storage)
- 3 Linkedin variables (pixel & credentials storage)
- 3 Helper variables (constants)
- 12 Google variables (pixel & credentials storage)
- 6 Facebook variables (pixel & credentials storage)
- 5 Extra variables (click IDs)
Not sure if there is a way to optimize this. The traffic source related variables are most of them “Lookup Table” variables to be able to use them with different domains (hostname). The Webhook payload has 45 fields, so each of them needs to be matched with an “Event data” variable.
And here it is, after adding the last Tag, which is the Pinterest tag, we’ve reached maximum capacity:
Ok, so I have been doing some research and I believe this is where most of the size is coming from (templates):
- Facebook: 21.4KB x 3 (Tags) = 64.2KB (facebook-tag/template.js at main · stape-io/facebook-tag · GitHub)
- TikTok: 14.8KB (tiktok-tag/template.js at master · stape-io/tiktok-tag · GitHub)
- Google: 16.9KB (gads-offline-conversion-tag/template.js at main · stape-io/gads-offline-conversion-tag · GitHub)
- Microsoft: 11.4KB (microsoft-ads-offline-conversion-tag/template.js at main · stape-io/microsoft-ads-offline-conversion-tag · GitHub)
- Taboola: 2.83KB (taboola-tag/template.js at main · stape-io/taboola-tag · GitHub)
- Outbrain: 3KB (outbrain-tag/template.js at master · stape-io/outbrain-tag · GitHub)
- Snapchat: 16KB (snapchat-tag/template.js at master · stape-io/snapchat-tag · GitHub)
- Reddit: 11KB (reddit-tag/template.js at main · stape-io/reddit-tag · GitHub)
- Pinterest: 13.3KB (pinterest-tag/template.js at master · stape-io/pinterest-tag · GitHub)
- Linkedin: 8.92KB (linkedin-tag/template.js at main · stape-io/linkedin-tag · GitHub)
- Twitter: 10.7KB (twitter-tag/template.js at master · stape-io/twitter-tag · GitHub)
This all sums up 194.45KB (max capacity is 200KB). Not sure if each Tag takes the whole JS tag size or if it is optimized somehow by Google.
Why are you running 3x tag for Meta?
I have all of these and have not hit capacity (not even seen this TBH).
I also have a-lot of USER-defined variables (100, which I admit i need to reduce), so something def a little up.
Yes, for Meta, I can indeed use just 1 Tag and 3 Triggers.
But for other ad platforms, I need 1 Tag per Event as the Conversion ID / Event ID changes. Meaning, it’s not based on generic Event Names but rather IDs.
@Chris_Bradley I remembered why I needed to have a separate Purchase tag in my case. That’s because the data flow is different. For PageView and Lead events I send the data via webhook POST call. But for Purchase event I send data via webhook GET call + Firestore lookup variables. So the parameters used in the Tag are different.
If the dataflow is difffernent you could write a template that adjusts it based on the inbound payload, might reduce tags.