Lectrium is ASC Certified
Every shopper interaction with Lectrium is reported as a standardized Automotive Standards Council (ASC) event in your dealership’s own Google Analytics 4, so you can trust the data and compare it with every other certified tool on your site.
What is ASC certification
One standard for how shopper activity is tracked
The Automotive Standards Council (ASC) publishes a shared standard for event tracking in Google Analytics 4 (GA4), Google’s website analytics platform, for automotive retail. An event is one recorded shopper action, such as switching a tab or submitting a form. The standard tells every certified vendor on a dealer website how to name and structure those events.
Because every certified tool follows the same rules, dealers can compare tools side by side and trust the data. An asc_form_submission from one certified vendor means the same thing as an asc_form_submission from another.
Lectrium was officially certified in April 2026, after hands-on testing of our tools on live dealer vehicle detail pages (VDPs). Testing covered every event, every required parameter and where each event was delivered. Lectrium is listed on the ASC certified products page.
ASC Certified since April 2026 · Tested on live dealer VDPs
What this means for your dealership
Lectrium data in your own GA4
Lectrium events land in your dealership’s GA4 properties with no setup. You never have to hand over a measurement ID.
Apples-to-apples comparisons
Lectrium names and structures events exactly like every other ASC Certified tool, so you can compare vendors side by side in the same reports.
Leads you can trace to your CRM
Every Lectrium lead carries a submission_id that matches the GA4 event to the lead record in your CRM.
How it works today · Live
How Lectrium events reach your GA4
Lectrium’s tools, including the Lectrium Dashboard and Lumi, Lectrium’s AI agent, run inside an iframe on your vehicle detail pages. An iframe is a frame that displays one web page inside another.
When a shopper uses a Lectrium tool, Lectrium sends an ASC event to your dealership’s GA4 properties. You do not need to give us a measurement ID, the code that identifies a GA4 property. Our tools find your GA4 properties on your website automatically, following ASC guidelines.
Website platforms store tracking settings in different ways, so we adapt delivery to each platform to make sure events reach your store’s own GA4 properties. If you want a specific GA4 property excluded, ask us and we will exclude it.
Every event carries event_owner = lectrium and product_name = lectrium_dashboard, so you can isolate Lectrium activity in any report.
Live on Lectrium dealer sites today
- STEP 1Shopper on your VDPUses range, charging or savings tools, or Lumi
- STEP 2Lectrium toolRuns inside an iframe on the vehicle detail page
- STEP 3Your GA4 propertiesReceive standardized ASC events
event_owner = lectriumWhere we’re heading · In progress
Where we’re heading: events from your own page
Until now, Lectrium events have been sent from inside the tool’s iframe directly to your GA4 properties. That gets the data into GA4, but GA4 can count the shopper inside the iframe as a different user from the same shopper on the rest of your site. That makes it hard to connect “used Lectrium” with “submitted a lead.”
Dealers asked us to fix that, so we are moving Lectrium’s ASC events onto your own page: into its tagging setup and its data layer (the dataLayer, the running list of events that Google Tag Manager reads). Here is what changes.
1. Same shopper, same session. A session is one visit to your site. Lectrium activity connects to everything else the shopper does there, so path and funnel reports work end to end.
2. Respects your consent settings. Events go out through your own page, so they follow your site’s consent choices.
3. Ready for Google Tag Manager. Google Tag Manager (GTM), the tool that manages the tags on your site, can use the events directly to trigger tags, build audiences and pass conversions, including asc_form_submission_sales, to advertising platforms.
4. No work for you. The events and parameters stay exactly the same.
We are rolling this out site by site, so it is not on every Lectrium site yet. Want this on your sites? Contact our data team.
In progress · Rolling out site by site
- STEP 1Shopper on your VDPUses range, charging or savings tools, or Lumi
- STEP 2Lectrium toolHands each event to your page
- STEP 3Your page and dataLayerEvents join your site's own tagging setup
- STEP 4Your GTM and GA4Same shopper, same session
Reference · Live
The ASC events Lectrium sends
Lectrium sends six kinds of ASC events, seven event names in all, because every lead is sent twice. Each one maps to a real shopper action inside the tool.
asc_menu_interaction records a shopper switching between sections of the tool. asc_element_configuration records a shopper personalizing the results with their own details, our strongest research signal. asc_cta_interaction records a shopper opening a key insight, the EV report or the contact form. asc_media_interaction records a shopper exploring the charging and range map. asc_form_engagement records a shopper starting or filling in a Lectrium form. asc_form_submission and asc_form_submission_sales record a completed form submission.
Event parameters are extra details attached to an event, such as the text of the button a shopper clicked. Only completed form submissions are reported as submissions.
Names and parameters follow the ASC GA4 standard
| Event name | Shopper action | Key parameters |
|---|---|---|
asc_menu_interaction | Switches between sections of the tool, such as Overview, Range, Savings or Charging. |
|
asc_element_configuration | Our strongest research signal Personalizes the results with their own details, such as daily driving distance, ownership period or home charging setup. |
|
asc_cta_interaction | Opens a key insight such as total EV savings, range or battery details, opens the EV report or contact form, or clicks a form's submit button. |
|
asc_media_interaction | Explores the charging and range map: zooming, panning or opening a charger. |
|
asc_form_engagement | Starts or fills in a Lectrium form, such as the dealer contact form or the EV report. |
|
asc_form_submissionandasc_form_submission_sales | Submits a Lectrium form. Every lead is sent as both events: the standard submission and the sales copy that advertising platforms use for conversion optimization. |
|
Reference
Parameters on every event
Every Lectrium event carries the same set of parameters, so you can filter and segment Lectrium activity and tie it to the exact vehicle a shopper was viewing. item_id holds the VIN, and event_owner is always lectrium.
To report on a parameter in GA4, register it as a custom dimension: a field you add in GA4 Admin so the parameter’s values appear in reports and explorations.
Open the table for the full list
What we do not send (and why)
Page views
Your website already sends asc_pageview for the VDP. A second one from Lectrium would inflate your traffic, so we never send it.
AI assistant questions
Conversations with Lumi are not sent to GA4; conversation analytics live in the Lectrium dealer portal. A lead submitted through Lumi’s form is sent as asc_form_submission.
Calls and chat events
Our tools do not include phone or live chat, so we never send asc_click_to_call, voice or chat events. We only report what actually happened.
Principles
How we decide what counts
No double counting. We never duplicate events your website already sends.
Real actions only. We report what a shopper actually did, never inferred or estimated activity.
Personalization is its own signal. A shopper entering their own numbers shows stronger intent than a click, so it is tracked separately as asc_element_configuration.
Forms are tracked in stages. Starting a form (asc_form_engagement) and submitting it (asc_form_submission) are separate events, so you can see where shoppers abandon a form.
Every lead can be tied back. Each submission carries a submission_id that matches the GA4 event to the lead record in your CRM.
Every event carries the vehicle. Events are attributed to the exact VIN the shopper was viewing.
Every event is labeled as ours. event_owner = lectrium makes Lectrium activity easy to isolate or compare.
Applied to every event we send
For analysts
How to measure Lectrium’s impact in GA4
Step 1. Register custom dimensions. In GA4 Admin, add event_owner, element_text, element_type and form_name as event-scoped custom dimensions. They only apply to data collected after you register them.
Step 2. Build a Lectrium segment. Include users with any event where event_owner exactly matches lectrium. For a stricter version, use only asc_element_configuration: shoppers who entered their own numbers.
Step 3. Find leads elsewhere on the site. Use asc_form_submission where event_owner is not lectrium, plus asc_cta_interaction for calls to action that open third-party flows.
Step 4. Build the views. Create an open funnel from VDP view to a Lectrium event to a non-Lectrium submission, a path exploration that starts from Lectrium events, and a comparison of lead rate for the Lectrium segment against VDP visitors who did not use the tool.
Tip. Use user-scoped segments and longer date ranges, because research and the lead often happen in different sessions.
Uses standard GA4 Admin and Explore reports
