Analytics · ScoutX → GA4 / GTM
ScoutX, GA4 and Google Tag Manager
Your container ID goes in and the site starts reporting events that mean something — not just page views, but the actions that indicate a shopper is close.
How it works
- Lead submissions, phone clicks, unit views and the steps of the shopping journey are pushed to the data layer as named events, so your agency builds conversions against them rather than inferring intent from page paths.
- Consent Mode is respected. The consent stub and the data layer initialise synchronously, before anything else, so events queued during page load are replayed into the container once it boots instead of being lost.
- Personally identifying information never enters the data layer. Anything in there is readable by every tag in the container and by anyone with developer tools open, which is the wrong place for a customer’s email address.
- Heavy third-party tags are deferred off the critical path — loaded after the first interaction, or after a short fixed delay so a visitor who never interacts is still measured. That matters more here than in most categories, because so much powersports browsing happens on a phone inside a social app’s in-app browser.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Questions
Google Analytics 4 & Tag Manager questions
Do we keep our existing GTM container?+
Yes. You supply the container ID; your tags, triggers and variables stay yours.
Will deferring tags lose data?+
Events fired before the container boots are queued and replayed, and a hard fallback delay means a no-interaction visit still loads the container.
Can we get the customer’s email into a tag?+
Not through the data layer — that would expose it to every tag and to anyone with devtools open. Server-side delivery with hashed values is the correct route, and it is supported.