I set up the way you described in the video and it working for me but I got a question or two.
I noticed that there is a bunch of invisible contacts with ip address on it no names or no email addresses.
It turns out that whenever any devices visit the confirmation page, either a live person, a bot or search engine, it will generate a contact card with just only their ip address.
I had to keep deleting those blank contact cards from the contact database.
I am just setting up an opt in to assign a btg tag to those that sign up for the Bridge the Gap newsletter with a tracking tag on the confirmation page when they click on the link in the confirm email address.
This is the string I use on confirmation page where members opts-in their email address
There are total of 11 contacts in the segment with btg tag … 8 of them have ip address only and it is hidden but it annoying to see it being counted when there is 3 with email and name attached to it while 8 are blank with ip address only.
Hi,
Originally I made 2 videos. The first video explains how to use a double optin procedure. It is relying on clicks in emails rather then visits in landing pages. The second one (the one you referring to) shows how to do without waiting for cronjobs. And yes, it has the disadvatage of passing the tag to any visitor. You can restrict that by only passing valid emails:
I did not have time to watch entire video but I think separate php script was created on website he is trying to track/get the info from.
The reason you get the above output after save is because your are copying the php code to editor that does not expect it (grapeJS). Your input is escaped for security reasons.
Also I would advise you use <?php /*code here*/ ?> tag to enclose php code since short tags might be disabled by configuration.
Has there been any change to this with compose version Mautic?
I deleted the Mautic and I did a fresh install using compose then add the new tracking number to the page but it no longer tagging new contact on new fresh install of Mautic using compose.
This is what I am using on my “Confirmed web page”
It still not tagging new contacts on my new mautic. I watched the video a couple of time and looked at my previous mautic but I can’t find any different between the two installation.
Is there an extra step for compose installed mautic?
There had to be something asmissed … I am not sure if I am missing something or not after reinstalling Mautic using compose instead of standard compressed files.
We think we may know what going on because there were other area that our Mautic was having issue at like the segment contact etc.
When we lift the function restriction on some of the function like shell_exec, the segment filtering start working again so maybe the same restriction was breaking this too.
It seems once the contact have confirmed then later deleted from Mautic. THat contact can no longer be re-tagged again if they fill out the form and click the confirmation link to direct to a page with the javascript to be assigned a tag.
When we deleted a contact then that contact can no longer opt in even if they go back and fill out the form again then click the link in email to go to the confirmation page. The tag will no longer assign to contacts that been deleted.
I already emptied the cache on Mautic and my browser also cleared the cookie. I was deleting contact to run the test again but it seems that once it been tagged before then it can never be tagged again after it been deleted.
Is there a way to reset that contact for testing purpose?