Understanding the dl_subscribe Event
Overview
The dl_subscribe
event is an essential data layer event that is used to capture user sign-ups for email and SMS marketing lists. The event is triggered when a shopper subscribes to email or SMS services through native Shopify forms, as well as third-party pop-ups (e.g., Klaviyo, Attentive, Postscript).
At Elevar, we maximize the amount of data thats captured by the data layer, and then send as much of that data back to your connected server side marketing destinations, and if we don’t have a server side destination for an event, we still always try to also maximize the amount of data that’s sent back to destinations through client side tracking technology and GTM. For businesses using Elevar, this event is important for optimizing marketing flows, thus ensuring that email and SMS sign-ups are accurately recorded. If your email form events aren't automatically detected, you can manually push these events using provided code snippets.
Importance of the dl_subscribe
Event
dl_subscribe
EventThe dl_subscribe
event is key to the functions provided by Elevar's, specifically for tracking email and SMS sign-ups.
Accurate Tracking of this Event Allows Businesses to:
- Collect actionable customer data for building marketing lists
- Improve targeted marketing efforts
- Analyze customer behavior to enrich session insights
- Support the effectiveness of abandonment flows in email/SMS providers (e.g., Klaviyo, Attentive, Postscript, Yotpo)
How the dl_subscribe
Event Enriches Audiences and Lists
dl_subscribe
Event Enriches Audiences and ListsThe dl_subscribe
event enriches customer lists by capturing data when users sign up for email or SMS communications. This data, such as lead type (email or phone) and customer properties (e.g., email address or phone number), is then pushed to Elevar’s data layer.
The data captured through this event helps businesses:
- Build targeted, segmented marketing lists
- Enhance personalization and customer engagement efforts
- Tailor marketing campaigns based on lead type (email or phone) and user behaviors
Impact on Flow Performance for Email/SMS Providers
The dl_subscribe
event enhances the performance of abandonment flows for email and SMS marketing providers (e.g., Klaviyo, Postscript, Attentive, Yotpo).
By capturing more accurate customer data, Elevar’s integration can boost the performance of abandonment flows by as much as 50-60%. This enhancement is largely due to Elevar’s ability to send high-quality data to marketing destinations, ensuring a higher conversion rate for customers who have signed up for email or SMS alerts.
What Happens if the dl_subscribe
Event Is Not Firing Properly?
dl_subscribe
Event Is Not Firing Properly?If the dl_subscribe
event is not firing correctly, it can hinder Elevar’s ability to enhance the performance of abandonment flows, which rely on accurate email and SMS data. Without this event firing properly, you risk missing valuable customer information and underperforming marketing campaigns. It’s essential to address issues with the event firing to ensure your marketing flows are as effective as possible.
How to Ensure the dl_subscribe
Event Fires Properly
dl_subscribe
Event Fires ProperlyAutomatic Handling:
If you are using supported providers like Klaviyo, Postscript, or Attentive, the
dl_subscribe
event should automatically trigger when a user subscribes via the native Shopify Footer or through pop-ups provided by these third-party services.
Ensure the event is firing correctly:
- Open your browser's developer tools.
- Check the
window.ElevarDataLayer
to see if it contains an item with an event property set todl_subscribe
.
Manual Event Pushing:
- If the event isn’t automatically picked up, you can manually push the
dl_subscribe
event using the following code snippet. This ensures the event is captured when an email or phone number is submitted via a form.- For email submissions:
-
window.ElevarDataLayer.push({ event: "dl_subscribe", lead_type: "email", user_properties: { customer_email: "[email protected]" } });
-
- For phone submissions:
-
window.ElevarDataLayer.push({ event: "dl_subscribe", lead_type: "phone", user_properties: { customer_phone: "7809510883" } });
-
- For email submissions:
Testing the Event:
- Once you have implemented the necessary code, test the email sign-up process on your website.
- You can inspect the event by navigating to the "Network" tab in your browser’s developer console and verify that the
dl_subscribe
event is being sent with the correct lead type and user properties (email or phone number).
- You can inspect the event by navigating to the "Network" tab in your browser’s developer console and verify that the
Troubleshooting: If the
dl_subscribe
Event is Still Not Firing CorrectlyIf the
dl_subcribe
event is still not firing correctly, you can do a few things:
- Ensure that the code is placed in the appropriate section of your website’s codebase or Google Tag Manager
- Double-check that the event is triggered correctly upon form submission
- Verifying proper event firing by inspecting the network activity using your browser’s developer tools. When a customer submits their email or phone number through the sign-up form (whether in the footer or pop-up), you should see the
dl_subscribe
event with the corresponding customer data.For a visual guide, refer to this screenshot, showing the successful firing of the event.
For more information on Session Enrichment and Email and SMS Sign Up Tracking, follow this guide!
Understanding the dl_subscribe event works with Server-Side and Client-Side Cookies
The dl_subscribe event has a significantly better impact with server-side cookies compared to client-side cookies due to the enhanced durability, accuracy, and reliability of server-side tracking. By using server-side cookies with the dl_subscribe event, you ensure long-term and accurate tracking, thus creating the base for advanced marketing workflows.
Summary of Impact:
Feature: | Client-Side Cookies: | Server-Side Cookies: |
---|---|---|
Lifespan | 7 days (Restricted by ITP/ETP) | Customizable (Weeks/Months/Years) |
Tracking Accuracy | Prone to data loss | High accuracy |
Privacy Compliance | Limited under strict browser policies | First-party, privacy-compliant |
Attribution | Limited to short attribution windows | Extended attribution windows |
Cross-Device Tracking | Fragmented | Unified |
Updated 14 days ago