Personyze Support Personyze Support docs
Open Personyze
Setup

Setup by Site Type — Tracking, Feeds & Integrations

Pick your site type — e-commerce, B2B/SaaS, publisher, or mixed — and follow the setup checklist for the tracking events, feeds, and integrations that apply to you. Avoids the trap…

Updated 29 minutes ago 8 min read
A
by Admin

The biggest mistake new Personyze users make is installing the tracking tag and stopping there. The tag alone gives you almost nothing useful. The real setup happens after — wiring up the tracking events, feeds, and integrations that actually power personalization for your kind of site.

This guide branches by site type. Pick the closest match below, follow that section’s checklist, and you’ll have everything Personyze needs to start producing meaningful results.

Which site type are you?If your site sells physical or digital products with a cart and checkout → E-commerce. If your site generates leads/demos/signups for a B2B product → B2B / SaaS / Lead Gen. If your site is content-driven (blog, news, media) → Content & Publishing. If you have multiple of these on one site (a SaaS with a content marketing blog, an e-commerce store with editorial content) → Mixed.

Universal first step — install the Personyze tag

Regardless of site type, the first thing is loading the Personyze tracking script on every page. This single snippet powers everything else.

Once the tag is loaded site-wide, jump to the section below that matches your site type.

🛒 E-commerce setup checklist

For online stores with products, carts, and checkout. The goal: Personyze knows your full catalog, sees what every visitor is interested in, and can recommend products / recover carts / personalize offers in real time.

1. Track product interaction events

Personyze needs to know when visitors view products, add to cart, and complete purchases. These three events are the foundation of every behavioral algorithm.

  • Product view — fire on every product detail page. Capture: product ID, name, category, price, currency.
  • Add to cart — fire when items are added. Capture: product ID, price, quantity.
  • Purchase — fire on order confirmation. Capture: order ID, products array, total, currency.

Full code samples and integration patterns: Setting Tracking for Product Interaction Events.

Special integrations available for Shopify stores:

2. Upload your product catalog

Personyze needs your product feed to render recommendations. Without it, recommendation widgets fall back to whatever metadata is in the page DOM — significantly less reliable. Three sync methods (pick one):

📄 CSV uploadOne-time or manual periodic upload. Simple but stale risk — re-upload whenever inventory or pricing changes meaningfully.
🔄 XML / JSON feed (recommended)Provide a feed URL — Personyze polls hourly/daily. Google Shopping XML format works natively. Best for production.
🔌 API pushBackend pushes catalog updates programmatically. Best for huge catalogs or real-time inventory accuracy.

Setup details: Setting the Product/Content Feed · Recommendation Data.

3. Connect optional integrations

  • CRM — if you have a HubSpot/Salesforce/Pardot list of customer attributes (lifetime value, loyalty tier, lead score), connect it for richer targeting. See CRM Integration.
  • Email platform — Mailchimp, Klaviyo, HubSpot, ActiveCampaign, Brevo. Lets you embed live recommendations into emails. See Open-Time Email Recommendations.
  • CDP — if you use Segment or Zeotap, route enriched user data into Personyze. See Segment Integration · Zeotap CDP.

4. First campaigns to launch

  1. Product Recommendations Wizard — start with category-page or product-page widgets.
  2. Cart Abandonment Emails — the highest-ROI campaign for most stores.
  3. Auto-Apply Coupon at Checkout — reduce friction on promotional offers.
  4. Buy Together Discount — bundle cross-sell with conditional discounts.

🏢 B2B / SaaS / Lead Generation setup checklist

For software companies, lead-gen sites, demand-gen funnels, and ABM-driven motions. The goal: Personyze knows which company is visiting (even when they’re anonymous), what their stage is, and personalizes the experience to convert them.

1. Track key page and conversion events

For B2B, the events that matter are page-level intent signals and conversion actions — not e-commerce events.

  • Page views are tracked automatically once the tag is installed. Special pages worth tagging: pricing, demo request, comparison pages, specific product pages.
  • Conversion goals — fire when a visitor submits a form, requests a demo, signs up, or hits any other key milestone. See Setting Conversion Goals Tracking.
  • Custom JS goals for in-app events that don’t have a unique URL — see Setting JavaScript Goals Tracking.

2. Connect your CRM (the most important step for B2B)

For B2B sites, the single highest-leverage integration is your CRM. Once connected, every known visitor’s CRM attributes — lifecycle stage, deal value, account tier, industry, segment — become available for targeting.

3. Add ABM data enrichment (optional but powerful)

If you want to identify anonymous B2B visitors — the people who land on your site before filling out a form — connect an ABM provider. They use IP-to-company resolution to tell you which companies are visiting, even from cold traffic.

ClearbitSetup guide — strongest in the HubSpot ecosystem, technographic depth.
ZoomInfoSetup guide — largest dataset, deepest firmographic data.
6senseSetup guide — buyer intent stage signals beyond just identification.
LeadfeederSetup guide — EU-friendly, GDPR-conscious choice.
AlbacrossSetup guide — free tier, EU-hosted, great for piloting ABM.
LeadrebelSetup guide — Swiss data residency for strict EU compliance.

4. Add custom profile fields if needed

For attributes not in your CRM — internal scores, in-session signals, custom flags — add them on the fly: Custom User Profile Fields.

5. First campaigns to launch

  1. CRM Targeting Wizard — show different content to known accounts vs. anonymous visitors.
  2. Popup & Banner Action Guide — exit-intent demo offers, segment-specific announcements.
  3. Dynamic CRM Variables in Content — personalize headlines and CTAs with company name, industry, etc.
  4. Targeting & Personalization basics — broader campaign mechanics overview.

📰 Content & Publishing setup checklist

For news sites, blogs, media properties, and any site where the primary asset is editorial content. The goal: Personyze knows what content exists, what each visitor’s interests are, and can serve relevant content recommendations and engagement campaigns.

1. Track content categories

Page views are tracked automatically. To power content recommendations, you also want to tell Personyze which category each piece of content belongs to (Technology, Politics, Sports, etc.):

2. Set up your content feed

For content recommendations, Personyze needs a feed of your articles, podcasts, videos, or other content items — same idea as a product catalog, but with content-specific fields (title, category, author, publish date, image URL, summary).

3. Set conversion goals that matter for content

For content sites, conversions usually mean: newsletter signup, account registration, paywall conversion, ad engagement, time-on-site milestones. Define these as goals so Personyze knows what success looks like.

4. First campaigns to launch

  1. Content Recommendations Wizard — “more articles like this” widgets at the bottom of every post.
  2. Web Push Notifications — re-engage subscribers without an email address.
  3. A/B Testing Wizard — test headlines, hero images, paywalls.
  4. Content Variations — show different content blocks to different audience segments.

🔀 Mixed / hybrid sites

Many sites are not purely one type. A SaaS company has a content marketing blog. An e-commerce store has editorial buying guides. A media property has a paid-subscription product. The good news: Personyze handles all of these patterns natively — just layer the relevant setups together.

SaaS + content blog

  • Follow the B2B / SaaS checklist as your primary setup (CRM connection, conversion goals, ABM).
  • Add the content tracking pieces from the Content checklist for your blog (categories tracking, content feed).
  • Run two parallel campaign tracks: lead-gen campaigns target your product/pricing/demo pages; content recommendations live on the blog.

E-commerce + editorial content

  • Follow the E-commerce checklist as primary (product tracking, catalog feed).
  • Add a content feed alongside your product feed — Personyze can recommend articles or buying guides on your store, weighted by behavioral interest.
  • Cross-link the two: a visitor who reads “How to choose running shoes” should get product recommendations of running shoes.

Multi-domain / multi-brand

  • Add all your domains to your Personyze account.
  • Enable Cross-Domain Tracking so a single visitor maps to a single profile across all your sites.
  • Optionally enable Cross-Device Tracking for visitor recognition across phone/desktop too.

Verify everything is working

Before launching campaigns, confirm the data flow is healthy. Three quick checks:

  1. Tag is firing. Open dev tools, network tab, filter for counter.personyze.com. Visit any page on your site — you should see a request fire.
  2. Events are firing. For e-commerce, view a product, add to cart — each should fire its own request. For B2B, submit a form / hit a goal — same check.
  3. Visitors and events appear in Personyze admin. Open Visitors Activity in Real-Time in your Personyze admin and watch yourself navigate. You should see your test session populate live, with all the events you fired.

If something is missing.If events aren’t appearing, the most common causes are: tag loaded too late (load it as early as possible — see GTM placement notes), event names misspelled (case-sensitive — product_view not productView), or SPA mode not enabled for single-page apps.

Next steps after setup

Once your tracking, feeds, and integrations are in place, you’re ready to:

  • Build your first campaign using the wizard most relevant to your site type (linked above in each section).
  • QA before launching — preview your campaign as different visitor profiles using the QA Simulator.
  • Measure what’s working — read the Performance metrics reference to understand attribution.
  • Scale gradually — start with one campaign per site type, learn what your audience responds to, then expand.