Budget: 4500 UAH Deadline: 2 days
Here, a short technical audit and corrections are needed, without unnecessary philosophy. I would allocate 1-2 days for the timeline, budget - 4500 UAH for checking the Meta Pixel, events, Weblium integrations, and bringing conversion tracking to a normal state =)
> We will check the Pixel through the Meta Events Manager, events on the main site and on the duplicate, possible duplications, different identifiers, script conflicts, GTM or manual Weblium inserts.
> If the problem lies in the structure of analytics, I would simplify it - separating events, traffic sources, and conversions so that advertising accounts do not mix data.
> As a result, I will provide a short list of reasons and technical settings that can be checked in the Events Manager.
Look, there’s a nuance here... for an accurate assessment, two things are needed - whether the Pixel on the duplicate is the same as on the main site, and whether the events were set through Weblium, GTM, or manually in the code.
Relevant examples of experience
> https://business.ingello.com/eva - e-commerce and systematic work with digital infrastructure, where data accuracy is important
> https://business.ingello.com/prime-eva - close to tasks related to advertising analytics, events, and business reporting
> https://systems-fl.ingello.com/ua - briefly about Ingello Systems and our approach to technical systems
Access to Weblium, Meta Events Manager, and, if used, GTM will be needed. Well, yes... without access, one can only build hypotheses, and that’s already guessing on coffee grounds, although no - a bit more expensive and less useful.
