Personalization is only as good as what the platform knows. This section covers everything that arrives
before a campaign is built: what the tracker records, what counts as a conversion, what a visitor has consented to, who
they are, and how your own data gets in.
The tracker
What the tracking code records on its own, and the situations that need it told something extra.
- Single-page applications — A site that never reloads has to tell the tracker when the page changed.
- Cross-domain tracking — Keep one visitor as one visitor across two domains.
- Cross-device tracking — Phone and laptop as the same person.
- Cookies — What Personyze stores in the browser, and for how long.
- Categories tracking — Telling Personyze which category a page belongs to.
- Product interactions — View, add to cart, purchase — the events recommendations are built on.
Conversions
- Setting conversion goals tracking — Wiring a goal to a real event on the site.
- JavaScript goals — The conversion pixel, for goals your site has to report itself.
Defining what a goal means, and reading the results, is
Conversion tracking under Analytics.
Visitor data
- Grab data from your site — Read values off your own pages into the session and the profile.
- User profile data — Custom fields, and keeping them in sync with your systems.
- Visitor attributes — Everything Personyze holds about a visitor and a session.
Privacy & consent
- Consent mode — Loading Personyze under a consent manager.
- GDPR & opt-out — Honouring an opt-out in code.
Feeds & uploads
- Uploading feeds & data files — Catalog, interests, content and users — by URL, upload or SFTP.
- Shopify e-commerce events — Purchases and cart events from a Shopify store.
- Shopify cart extension — Tracking through Shopify’s newer checkout.