• Hello,

    I’ve activated browser + (API) server tracking.
    They both trigger and works!
    But the CAPI sends events …1 minute later.
    So browser events and server events do not match. See picture below:

    https://imgur.com/SpDVfS3

    What should I do to solve this issue ?

    Thank you very much,

    PS: Do not advise upgrading hosting, my hosting is a dedicated one and very fast.
    And fyi, I use LiteSpeedCache.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author PixelYourSite

    (@pixelyoursite)

    We send them in real time, as you can see if you check the reported time for each event. However, the testing tool has some delay when reporting server events.

    The events you have in your screenshot are different events, that’s why they have different IDs. Please watch this video, and apply the fix explained there. Change from hooks to classes: https://www.youtube.com/watch?v=oZoAu8a0PNg

    Thread Starter martymcfly2015

    (@martymcfly2015)

    Thanks for the quick reply.
    At first, I had a ATC problem so I already changed from hooks to classes and from now, the ATC trigger works perfectly.

    However, the delay on CAPI is not especially on ATC, it’s on ALL EVENTS (Page view/ATC/ITC/Purchase).
    What could be the issue then ?

    Thank you very much for your support!

    Plugin Author PixelYourSite

    (@pixelyoursite)

    As mentioned before, the testing tool has a delay in showing the API events, we send them in real time.

    But your screenshot shows two separate events, that’s why they have different event IDs.

    I suspect your other API events have the same event ID as the corresponding browser event. And if you check their reported time, you will notice that there is almost no difference between the browser and server event’s time.

    Thread Starter martymcfly2015

    (@martymcfly2015)

    Thanks for the quick support, you’re amazing!

    I’ve runned another test and this is what I discovered in detail :

    https://imgur.com/7x1rPtB

    Indeed, the server and browser are triggering the same event ID (PageView/ITC/Purchase).
    But for ATC, they trigger different event ID.
    ATC is the most important event to do retargeting, so how can I solve this issue ?
    Do you have another idea?

    Thanks a lot ! ??
    Highly appreciate your support, i’m convinced for the PRO version !!

    Plugin Author PixelYourSite

    (@pixelyoursite)

    ATC – you need to change between classes or hooks, and see what works for you.

    Thread Starter martymcfly2015

    (@martymcfly2015)

    Here is the comparison of my test:

    Hooks: I have 1 event trigger from Server (API only)

    Class: I have 2 events trigger: one from browser and one from server (api) so it’s perfect BUUUUT they have both different ID so I guess Facebook count 2 Add To Cart in that occasion.

    From your experience and based on my comparison, what would be the best ?
    Hooks or Class ?

    Personnaly, I would say Class, because even if it trigger twice the ATC, at least I have a double chance to collect data!
    And arriving at the checkout, the server and browser show the same event ID so the amount will be updated anyway.

    What’s your final answer?
    Thank you very much!

    Plugin Author PixelYourSite

    (@pixelyoursite)

    I would go with classes.

    However, it’s quite strange, what theme do you use?

    Thread Starter martymcfly2015

    (@martymcfly2015)

    Razzi Theme

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘CAPI delayed issue’ is closed to new replies.