Video

Thanks for your comment. The truth is you want the genuine customer reviews to be mainly positive. If your product is mostly getting negative reviews then you might have a product issue which will hurt your customer LTV and needs to be addressed. If you're getting mainly positive reviews and you have a few negative ones, I wouldn't worry about this, as it's to be expected. No brand can make every single customer happy at scale. If the reviews are outright lies or spam, then deffo hide them.

Hi there, it is refreshed every month

@@imjacknewman omg thankyou

You're welcome!

In which case, I would say there is likely an error with your domain. Either the SSL cert isn't active for your domain, or some other related error. It's not one that I commonly come across as being an issue.

@@imjacknewman it sorted itself out I don’t know if it just took longer for everything to align between stape configuration and other stuff but we are good how ever I did make one mistake. I used the business account ID instead of the ad account so I had to go back and change for the variables but we are good now. Just trying to make sure my ads are getting the info. Totally new to this. Ready for the next video or steps after this to make it more efficient and accurate. Thanks for all your help

Hi there, I'm glad you found it useful. You will need to hash the data via GTM, but the method will depend on how you are pushing information to Meta or Google etc... I use Adsmurai for Meta, which hashes the data for me prior to sending it elsewhere.

@@imjacknewman thanks for letting me know that. I'll look into it as I'm not using Adsmurai

Hi there, this is completely normal for it to say the firing status is failed and is actually just an error on the tag that should be ignored. The important thing is that when you go into facebook to test the events, that both the browser and server side events pull through and deduplicate. Provided that happens, then the conversion api is working exactly as it should be and you are fine to push it to production.

@@imjacknewman Thanks! Seems to work perfectly almost 2 weeks in :)

Hi there, provided they have the exact same event ID, then it may be a processing delay on Meta's end.

@@imjacknewman Thanks! Strange because the events are just side by side but not grouped together like the PageView.

Hi there, that would vary massively depending on the platform you are using to build your site, so it wouldn't be possible to do a generic video on this. I do have a video on how to do so with Go High Level, so that may provide you some insights.

Hi there, this is completely normal for it to say the firing status is failed and is actually just an error on the tag that should be ignored. The important thing is that when you go into facebook to test the events, that both the browser and server side events pull through and deduplicate. Provided that happens, then the conversion api is working exactly as it should be and you are fine to push it to production.

Hi there, that would vary massively depending on the platform you are using to build your site, so it wouldn't be possible to do a generic video on this. I do have a video on how to do so with Go High Level, so that may provide you some insights.

Hi there, I use a Sony Alpha ZV-E10L.

Hi there, this is completely normal for it to say the firing status is failed and is actually just an error on the tag that should be ignored. The important thing is that when you go into facebook to test the events, that both the browser and server side events pull through and deduplicate. Provided that happens, then the conversion api is working exactly as it should be and you are fine to push it to production. Regarding the Beehiiv newsletter, it's not a platform i've come across before. Sometimes in the tag manager preview, you can see a history change event that has parameters specific to it which would be used as a trigger. But without seeing it myself, I wouldn't be able to comment any further.

@@imjacknewman Hey Man thanks for responding so fast. For PageView, both the browser and server side events are pulling through and deduplicating so that's solved. 👍 Regarding Beehiiv, for the Lead tag, I used the History Change trigger and set the 'Page URL contains' condition accordingly under 'Some History Changes' and it's working well and reliably. Both the browser and server side events are pulling through and deduplicating. 👍 I'm now just trying to figure out the data layer variable piece to push the captured customer's email through as the Lead event tag fires. Is it simply a matter of setting the variable up with the correct naming convention and version then adding it as a 'customer information parameter' within the Lead tag itself? Thanks again bud!

Hi there, every platform pushes data differently, so I wouldn't be able to provide an exact run down of how to do so. I do have a video on how to do so with Go High Level Forms, so that may provide you some insights.

It depends on if there's a prospect on getting the data you need without paid media. In some cases, it can be beneficial to run some initial well thought through paid media to speed up this process, but the expectation with these shouldn't be performance, it should be data gathering and learning.

@@imjacknewman Thank you so much!

There us no difference in performance between the two, it just preference for set-up at this point.

With lookalike audiences, the lower the %, the closer the audience is going to be to the base audience you are using to create the lookalike. Lookalike audiences are reductive in their nature, meaning that there are only so many people that will fit within that range and it doesn't replenish itself in the way that a broad audience would. Essentially, as you run them longer, you're decreasing the number of new people that your ads are able to be shown to, which can be indicated by increases in ad frequency.

Is there a possibility for a dynamic upload of a customer lookalike lists via SFTP? Then the list participants would change and would also be suitable for long term use.

Hi there, this is completely normal for it to say the firing status is failed and is actually just an error on the tag that should be ignored. The important thing is that when you go into facebook to test the events, that both the browser and server side events pull through and deduplicate. Provided that happens, then the conversion api is working exactly as it should be and you are fine to push it to production.

Hi there, thank you. Most data isn't in the data layer innately and requires some sort of additional JS push, which unfortunately varies massively from platform to platform. Because of this, it isn't really possible to go through the steps for every platform. I do have a video on how I do this for Go High Level, which may provide you with a starting point for elsewhere. Click ID is a built in variable in GTM. If you go to variables and click configure under the built in variables, you can enable this. Just note that this will not be the click id from Meta, it will be a separate parameter.

@@imjacknewman I saw the video, it was exactly what I was looking for. I also need to do the same for an wordpress/ Elementor website but I'll try to work out the JavaScript. Thanks a lot!

Glad i could help

My default thinking is that it's actually likely a visual glitch that can sometimes happen in the ads manager. Provided they have the exact same ID, then it is completely down to Meta to deduplicate and there wouldn't be much else you're able to do. Step 1 would be to refresh the screen/give it a couple of minutes and see if it's a visual glitch or Meta being slow in processing the data.

Thanks - this platform is GoHighLevel

@@imjacknewman Thanks

The best you'd get potentially is trying to use the fbc url parameter that it loads when you click to an external site, or attempting to pull the values from the cookies that it loads, but third party cookies are getting more and more difficult to use. Though this will also have a very minimal impact on the event match quality, as direct customer data like email and phone number count the most for matching.

Do you mean it pulls through single server and browser lead events, or multiple browser events are firing for example? If it's the former, are they pulling through with the same event ID or are they different?

@@imjacknewman I mean that there is 1 server hit and 1 browser hit so I have 2 hit counted has 2 different events. This 2 hits doesn't get deduplicated. That's very strage cause talking about custom event this is not happening. I sent a video on your email.

Thank you

Pushing things like customer email address, phone number, names etc... will all do this. But I wouldn't be able to do a specific video on this, as the way you would collect this information and push it into google tag manager varies based on platform.

It doesn't pull it through on it's own, so you would need to configure this.

Thank you

Aha thank you very much

Hi there, this is completely normal for it to say the firing status is failed and is actually just an error on the tag that should be ignored. The important thing is that when you go into facebook to test the events, that both the browser and server side events pull through and deduplicate. Provided that happens, then the conversion api is working exactly as it should be and you are fine to push it to production.

The method will vary massively depending on what platform you use, so there isn't a generic explanation unfortunately.

Thank you :)

The domain name 100% doesn't have to be the domain you want to track, it is just used on the back end to send information between Google and Meta. Without seeing things myself I wouldn't be able to diagnose your problem unfortunately.

Hi there, thanks! You would need to change your set-up so that you are using solely the Adsmurai tags, otherwise you are likely to get double reporting due to no deduplication being able to happen from a Custom HTML tag.

@@imjacknewman Thanks a lot Jack! I'll give it a try

No problem!

Hi Declan, just to check, did you set up a separate tag specifically to fire off the page view event?

@@imjacknewman I just checked again and I did. The facebook page view is showing up on events manager via the browser but not server whereas all my custom events are showing browser and server. Does it matter once the custom events are working and the page view is showing browser?

Heya, it's not something i've personally done, but at a similar starting point to pulling standard form data; I would look at the local storage to see what data is pushed to it during that process. Unfortunately GHL definitely isn't fully there tracking wise at the moment as a full ecommerce platform, so it is likely to be a hodge podge of different custom script variables.

@@imjacknewman thanks so much, I raised it directly with them after commenting here too, let's see what they say, that's the problem with so many all in one platforms, they don't think about this kind of stuff... Thanks I'll definitely be implementing the form one anyway 😀

@@imjacknewman thought I'd update you - I've found a way to do it - my client was using a custom TY page but I just realised there is actually an Order Confirmation Element, so as long as you stick that somewhere on the TY Page you can pull the parameters from there using CJS - this works for me, something along the lines of: function(){ return document.querySelector("div.oc-product-description > span:nth-child(1)").innerText } I'm buzzing, there was no dynamic way of tracking any purchase data before, and their workflow actions are horrendous for CAPI events too, the only trigger that works with CAPI for order form doesn't allow you to use the "order total" custom field, it's a joke 😅 Just had to share anyway, this has been bugging me for about a week 😄 Thanks so much for the _UD inspo too 😊 Sophie

The label normally show as being marked as failed, it's a bug on the tags themselves but they do send through to Meta. For the purchase, it can take a few minutes to come through on the server side and you may also need to refresh your screen when in the events manager.

Provided you have the test event code in, it should eventually pull in the server side data. In some cases it can take a couple of minutes to pull through, as well as needing to refresh your screen due to a visual glitch.

Provided you have the test event code in, it should eventually pull in the server side data. In some cases it can take a couple of minutes to pull through, as well as needing to refresh your screen due to a visual glitch.

Thank you!

@@imjacknewman Are you thinking of releasing some updated methods to best launch PMAX campaigns for lead gen?

I have a few different videos in the pipeline at the moment, but that's a good idea.

Glad it helped

The parameters are set directly within the browser tag. How you pull the data from your site will differ massively depending on what platform you are using, but my video on how to pull data from Go High Level should give you some insight at minimum - czcams.com/video/wZqRYio6Hrc/video.html

Hi there, please check and make sure that you have the browser container tags set to fire both browser and server side. I would also double check that you have the correct server url on both your browser and server containers.

Thank you 🙌

Exactly! It's a full set-up with redundancy built in, which is recommended by Meta. In terms of purchases, you would just change the event that the browser tag fires off to being a purchase. I'm not entirely sure on whether teachable pushes conversion data to the data layer, but if it does natively, then you should basically be able to do some of the later stages from my GHL video, but instead creating a data layer variable instead of a js variable - czcams.com/video/wZqRYio6Hrc/video.html