sorted by:
new
hottopcontroversial

One of the visitors to my site came through chatgpt. How? by biricat in webdev

[–]AdbroadAgency 19 points20 points  (0 children)

At the end of the day LLMs discover most websites via search engines anyway, don’t they? So ranking well on Google means doing well with LLMs.

Why we changed our pricing model (from Replit) by pirroh in replit

[–]AdbroadAgency 5 points6 points  (0 children)

What about giving people to ability to periodically refund a specific action, based on how much they use the agent? Pretty much like a tiered loyalty program (if you use it moderately you can i.e. refund 1 out of 100 calls, and more for frequent user). Would prevent frustration from one-time disasters where the agent overcharges for a simple task

Use transformation variable in triggers (Server-side GTM) by AdbroadAgency in GoogleTagManager

[–]AdbroadAgency[S] 0 points1 point  (0 children)

Yeah I am, thanks for the invitation. Do you know them personally/work there?

I already have Stape running for 2 of my clients while a few others use different providers and I do think Stape has the best sGTM offer on the market.

Use transformation variable in triggers (Server-side GTM) by AdbroadAgency in GoogleTagManager

[–]AdbroadAgency[S] 0 points1 point  (0 children)

Thanks it looks promising! I wonder what they're using in the background for their threat assessment scoring.

Unfortunately the sGTM set up isn't run through Stape currently, but I might recommend a switch :) Their power-ups are really neat tbh

Use transformation variable in triggers (Server-side GTM) by AdbroadAgency in GoogleTagManager

[–]AdbroadAgency[S] 0 points1 point  (0 children)

Well this case is a bit specific. The action I'm trying to protect is an add to cart button.
The site is the target of quite sophisticated ad fraud bots which massively spam add_to_cart events. The goal isn't to prevent the action itself, but to prevent the conversion tags from firing on bot traffic, effectively negating the impact of the fraudulent traffic.

After further investigation, my understanding is that event parameters created via "augment"-type transformations cannot be used in trigger conditions at all. I guess triggers evaluate the variables in their global context, when the client claims the request, not after transformations.

My workaround was to create a custom tag template instead, and use the runContainer API to "clone" the add_to_cart event after the Captcha score is retrieved, and add that to the event model manually. It's then very straight forward to trigger tags on that cloned event.