Built integrations

Platforms

Pixels

Other

Conversion API

There’s no difference between the Conversion API and for example the Meta Pixel. We don’t use the Meta Pixel (and other pixels) because it can be blocked. We are experts in data collection and know which methods to use for sending data. All platforms have a Pixel, but we don’t use them! All platforms also have a kind of Conversion API where we send data.

We listen to Shopify’s webhook and receive data for purchases, initiated checkouts, and add-to-cart events. This data is then sent to the Conversion API.

For page views, we add an init script to the head of the page. This script sends data back, which we then send to the Conversion API.

Referral program

wetracked.io have a referral program wherein, you can earn while referring our service. It's as easy as letting them sign-up on our app using your unique referral link You can share your referral link to your friends, followers or anyone you know who's looking for great tracking service. The advantages of doing this are:

  • Your referalls will get 10% discount off their first 3 months + 14-day free-trial
  • You will earn 10% of what they pay to us
  • There's no limit with how much you can earn.
  • You can easily request a pay-out after you earned $50 only To learn more, you can visit the link: https://app.wetracked.io/referrals

    • Over reporting

    Customer had issue of over-reporting within thier ads manager. When over-reporting issue occurs, it is important to establish for which store/funnel it was and then proceed with the sanitary check. When doing sanitary check you should look for the following:

  • Check the store for any other source that may be sending data to the pixel as well (other tracking apps). This can be something simple as Facebook & Instagram app having data-sharing enabled (or other native ad platform apps) or they may have third-party trackers like Omega, Pixelio, Orichi and etc. Esentially you want to search for anything that can have the pixel customer has with us connected there.
  • You should also check for any third-party scripts that may be present on the store, especially in the theme files. You can check for scripts within: Settings > Checkout (scroll down, there should be 2 fields for additional scripts) , Online store > Preferences (again scroll a bit down, there should be a field where customer may have some tracking scripts present) , and finally as already mentioned do a detailed check of their theme files. Also you can run a quick test to check that no source sending data was left on the store. For this you can make use of the pixel extensions (currently there is one present for Meta, TikTok and Snapchat). Those extensions will show you the pixels present on store. Now, as we don't expose their pixels to the browser, this extension should not show pixels they connected with us when initiated on thier store. If the extension shows pixel they have with us, that means there is still other source present on their store that's connected with that pixel. *Extensions can be found and downloaded within your browser (extensions web store). Once you completed the sanitary check and established the source of over-reporting, you can message the customer what was the inital reason of over-reporting. Disclaimer: Please do not remove any source that is sending data to pixel / ad platform that they do not have connected with us. If however, you finished sanitary check and established there is no source causing over-reporting in customers case, there is still one thing to check, but this should always be your last resort. The last thing to check is if customer has ads in learning phase. When ads are in learning phase, ad platform tends to use modeled data, which is attributed within ads manager as well, to esentially push the ads out of the learning phase to active phase. Please note this happens occasionally, and should only be considered when sanitary check proved there is indeed no source feeding the pixel besides us. If customer has ads in learning phase, and sanitary check proved there is no third-party source, then this is most likely causing over-reporting of data, and it will resolve itself. In that case, educate the customer of this, and explain it's the ad platform that is performing it, and that the ad platform knows the best, and that it should calibrate itself soon as well. Quick tip: You should always make sure customer is using according pixel in ads manager (the one they connected with us) and you can also check their events manager to see if facebook received the same amount of data we sent there for that particular date. This should be considered for any data analysis with customer, not only if over-reporting is in question. Time zones matching between ads manager and store can also be checked.

    • About UTM Parameters

    UTM parameters are parameters set by the ad platform for you to recognize where the visitor is coming from. However, if the customer uses multiple devices and switches from one device to another, you may not be able to accurately track where the customer is coming from with UTM parameters. On the other hand, the ad platform can use advanced matching techniques using email address, first name, last name, IP address, etc., to bridge this gap in tracking. Therefore the data in your Ads manager is much more accurate and complete. And that's what we unlock for you by sending data accurately to the ad platform.

    Track new customer Purchase (Meta, Google)

    Every purchase event is being sent with an event parameter called occurrence, which has values of either first or subsequent. first indicates a purchase from a new customer, while subsequent indicates a purchase from an existing customer who has purchased before. This is only for Shopify.

    Scripts