Voyado CRM on Frntkey
Voyado connects to the Frntkey storefront through GTM event hooks. Standard ecommerce events (view_item, add_to_cart, purchase, sign_up) already fire from the storefront. The merchant configures the Voyado tag in their own GTM container.
Voyado is the default CRM choice for a large share of Frntkey merchants on Norce. The integration runs through Google Tag Manager: the storefront emits standard ecommerce events, and Voyado's GTM tag consumes them and updates the customer record. No server-to-server integration to build. Configuration is per-merchant, activation is per-project.
- GTM event stream pre-wired
- Standard ecommerce events emitted
- Works with Norce and Shopware
- Nordic retail CRM default
Benefits
GTM-first, no server integration
The Frntkey storefront emits standard ecommerce events (view_item, add_to_cart, purchase, sign_up) into the GTM dataLayer. Voyado's GTM tag consumes those events. No custom event schema to build per project.
One event stream, three consumers
The same event stream that feeds Voyado also feeds GA4 and Meta Pixel. Analytics, ads, and CRM share one data source. Changes to what data flows can be adjusted in GTM without touching the storefront code.
Backend-agnostic
Voyado is agnostic to the commerce backend. Running Frntkey on Norce or on Shopware makes no difference to the Voyado event stream. Product, order, and customer IDs are normalized by the GTM layer.
Days to activation
Once the merchant has a Voyado tenant and a GTM container, event collection starts working immediately after tag installation. Most Frntkey projects have Voyado collecting data within days of go-live.
What Voyado is
Voyado is a Swedish CRM and customer data platform for retail. It handles loyalty programs, email marketing, SMS campaigns, customer segmentation, and behavioral triggers. Its customer base leans toward Nordic mid-market and enterprise retail brands, and it is the default CRM choice for a large share of Frntkey merchants on Norce.
Voyado is not a checkout, a search engine, or a review platform. It is the customer relationship layer: who bought what, when they bought it, what they browsed, and how the brand communicates with them after the purchase. In a headless ecommerce stack, Voyado sits alongside the commerce backend (Norce or Shopware) rather than inside it.
How Frntkey integrates with Voyado
The Voyado integration on Frntkey runs through Google Tag Manager (GTM) event hooks, not a direct server-to-server API. This is deliberate. Voyado's data model is event-driven: purchases, page views, cart events, product interactions, and identity captures all arrive as tracked events. GTM is already configured in the Frntkey baseline for GA4 and Meta Pixel, and Voyado's data collection plugs into the same event stream.
In practice, the Frntkey storefront emits standard ecommerce events (view_item, add_to_cart, purchase, sign_up) at the right lifecycle moments. Voyado's GTM tag consumes those events and updates the customer record in Voyado. The merchant configures the tag in their own GTM container against their own Voyado tenant. Frntkey handles the event emission; Voyado handles the customer record.
What ships pre-wired
- Standard ecommerce events emitted on the storefront (view_item, view_item_list, add_to_cart, remove_from_cart, begin_checkout, purchase, sign_up)
- GTM dataLayer already populated at the right lifecycle moments
- Voyado tag template documented for the merchant's GTM container
- Identity capture on sign-up and post-purchase for logged-in customers
- Voyado newsletter and preference-center linking from account pages
- Order data enrichment (product IDs, categories, price) in purchase events
The merchant provides their own Voyado tenant, their own GTM container, and configures the tag. Frntkey ships the events and the storefront hooks; the merchant owns the CRM configuration.
What GTM-based integration means in practice
Running Voyado through GTM has real advantages and real limits. On the plus side: no server-to-server integration to maintain, no separate deployment cycle, changes to what data flows to Voyado can be adjusted in GTM without touching the storefront code, and the same event stream feeds GA4 and Meta Pixel without duplication.
The limit is that GTM is a client-side event pipeline. Events fire from the shopper's browser. Ad blockers, browser tracking prevention (Safari ITP, Firefox ETP), and consent management all affect whether events reach Voyado. For merchants who need server-side event delivery, Voyado's server-side ingestion API can be added as a project scope item. The GTM baseline covers the majority of Frntkey merchants without that additional work.
Voyado on Norce and Shopware
Voyado is agnostic to the commerce backend. Whether Frntkey is running against Norce or Shopware, the event stream to Voyado is the same. Product IDs, order IDs, and customer IDs come from whichever backend owns them; the GTM layer normalizes them into the event shape Voyado expects.
Merchants running Voyado alongside Norce typically also connect Voyado directly to Norce for CRM data enrichment beyond storefront events (order history sync, customer service data, offline purchases). That direct connection is separate from the Frntkey storefront integration and is managed between the merchant, Voyado, and their Norce configuration.
Setup timeline
Voyado activation on Frntkey is a configuration exercise, not a build. Once the merchant has a Voyado tenant, a GTM container, and the Voyado tag template installed, event collection starts working immediately. Verification against Voyado's incoming event view confirms the pipeline. Most Frntkey projects have Voyado collecting data from the storefront within days of go-live, not weeks.
When Voyado is the right choice
Voyado is the default CRM recommendation for Frntkey merchants selling to Nordic consumers with a loyalty or email marketing motion. It fits the merchant profile Frntkey serves: mid-market retail, Nordic customer base, structured product catalog, defined loyalty program. For merchants outside that profile — pure B2B without a loyalty layer, or D2C merchants using Klaviyo or Rule instead — Frntkey's GTM event stream feeds those tools equally well. The event schema is shared; the CRM tag is the variable.
Frequently asked questions
Ready to talk?
See how Frntkey fits your stack. Book a 30-minute demo.
Book a demo