Google Ads Conversion Tag Trigger Not working

Data collection and tags
1

Hello,

I have created a Google Ads conversion tag but the trigger isn’t firing. I have checked it multiple times and it seems like it should work. The trigger logic is:

Page URL regexp match ^https://www.fvdublin.org/in-person-event-registration-thank-you/?ad_chid=.*$

(which = “starts with”)

In debug mode, this “thank you” URL is always there. Here’s an example string that the trigger doesn’t work on:

Page Url
“Schedule A Tour | Senior Retirement Community | Columbus OH | Friendship Village of Dublin”

What might be happening here?

2

Hi! Just go with

with “contains” rule, I don’t see a need to use regexp here :slight_smile: or just “thank-you” as pattern, if you have multiple of thank-you pages

Cheers!

3

“?” is a special character in Regex - if you want to match a literal “?”, you should escape it using “\?”

So if you need to use this regex, I would try something like this:

^https://www\.fvdublin\.org/in-person-event-registration-thank-you/\?ad_chid=.*$
4

@sararekowska,

I tried your REGEX then also tried simply contains “Schedule A Tour | Senior Retirement Community | Columbus OH | Friendship Village of Dublin” as recommended by @gonerator.

Neither worked. Oddly, the internal form goal tracking works perfectly. To summarize:

THIS WORKS FOR INTERNAL GOAL:
URL contains Schedule A Tour | Senior Retirement Community | Columbus OH | Friendship Village of Dublin

(side-note: goal tracking set-up uses “URL” while the tag manager uses “Page URL” - is there is a difference?)

NEITHER OF THE FOLLOWING WORK FOR GAds TAG TRIGGER:

Page URL regexp ^https://www.fvdublin.org/in-person-event-registration-thank-you/?ad_chid=.*$

Page URL contains contains Schedule A Tour | Senior Retirement Community | Columbus OH | Friendship Village of Dublin

What is going on on??

5

I noticed that in the initial regex you mentioned there is “?ad_chid”, but when I go to the website it’s “?ad+chid”. Can you try again with the plus sign?

6

@sararekowska

I have no idea how you’re seeing “ad+chid” instead of “ad_chid.” The platform on which the forms are built is ActiveDemand and it, similar to Google’s UTM codes, it only uses “ad_chid” (explained in detail - https://engage.activedemand.com/hc/en-us/articles/360047169913-Integrating-ActiveDEMAND-with-Google-Services)

I just checked the Piwik Pro pages report and did two searches for the past 30 days:

URL contains “ad_chid”: 106 URLs found
URL contains “ad+chid”: 0 URLs found

Perhaps your browser is doing something?

Over the weekend, I compared the fvublin.org domain’s trigger logic to the trigger logic in another domain in the same instance, thebaileyatbridgepark.com. For both domains, I use the same exact trigger logic (URL contains) but FVD doesn’t work.

I must be missing some minor detail.

7

The only difference I see are the multiplicity settings:

image
image863×278 12.7 KB

Maybe that’s why it’s not firing properly? Or is it intended?

1 Like
8

That fixed it! Having a Charlie Brown “that’s it!” moment right now! (for reference: https://www.youtube.com/watch?v=F1VPJA3ZQwc)

This trigger’s purpose was to fire a GAds conversion tag but the trigger failed unless set to “many times” per session. Oddly, the trigger only fires once in my testing but that’s enough.

9

I’ve recently had a similar issue with the Multiplicity settings, the conversion was not firing even when I started a new session.

I wanted to create a trigger for a specific page URL that only fires once per session, but then I was forced to switch to “Many times during a session”.

10

@joao

The odd thing about the problem I encountered is that the trigger was not firing at all. In other words, when “once in a session” was selected, the trigger never fired. This seems to be a bug.

11

@David_Culbertson yes, that’s exactly what I encountered too, the conversion just wasn’t firing, and in the debug window I could see that it wasn’t firing because of this multiplicity condition.

I didn’t spend a lot of time debugging this behaviour in great detail because I was running short on time, but it seemed like a bug to me too: maybe there is an issue with the cookie that stores this information?

12

Thank you both for your input, I’ll look into this issue :slight_smile:

1 Like
13

I tried the setting on a couple of tags and it worked correctly - fired just once. Maybe in this case the session wasn’t closed yet?

14

No explanation, @sararekowska. I must have missed something during debugging but working fine now.

15

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.