Skip to content
  • There are no suggestions because the search field is empty.

Personalization for Deploy Experiences

Deliver Dynamic, Personalized Web Experiences for Every Visitor Using Convert Deploy

THIS ARTICLE WILL HELP YOU:

Availability: 1:1 Personalization is available on the Nexus Basic and Nexus Pro plans. If your account is on a different plan, contact Sales to upgrade. Plans overview: Source: Convert Pricing

What is 1:1 Personalization?

1:1 Personalization lets you create personalized Deploy experiences using placeholders (variables) that are filled with values you provide—via CSV uploads. Marketers can define variables per experience and use them to personalize text, images, colors (hex), HTML, CSS, or JS.

Key capabilities
  • Define reusable placeholders at the project level
  • Import visitor or group data via CSV
  • Insert placeholders inline in the Visual Editor using
  • Preview a single visitor/group record before publishing
  • Target by using existing audience or new rules i.e. Has visitor Data & Visitor ID

Personalization data is only used in Deploy experiences for this first release.

Prerequisites & Permissions

  1. Plan: Nexus Basic/Pro.
  2. Project consent toggle (compliance): Admins must enable Personalization at Project → Configuration → More Settings to acknowledge GDPR responsibilities and unlock the feature.

We recommend reviewing your CMP/consent setup if you set or use any cookies when personalizing. Source: Integrate with Cookie Consent Management Platforms (Cookiebot)

Step 1 — Enable Personalization on the Project

  1. Go to Project → Configuration → More Settings
  2. Toggle Convert’s Personalization and accept the compliance notice.
    Enable-Personalization
    Enable Personalization Toggle Message
    Enable-MessageDisable Personalization Toggle Message
    Disable-Message

Step 2 — Import Visitor/Group Data

You can supply values for each placeholder per visitor or group record.

CSV Import

Format

  • The first row contains headers = placeholder keys (e.g., visitor_id, first_name, company_name, amount_saved, cta_text).
  • Subsequent rows contain values.

File type: standard CSV exported from Excel/Google Sheets/LibreOffice.

IMport-CSV

Example CSV

visitor_id,first_name,company_name,amount_saved,cta_text

john_123,John,Acme Inc,25%,Start your 15-day trial

jane_456,Jane,Globex,€120,See pricing

If your spreadsheet tool exports a non-CSV MIME type, the upload may fail. Re-export as CSV and retry. (In general, use text/csv from Excel/Sheets/LibreOffice.)

Step 3 — Create & Manage Placeholders (Variables)

Create your variable list (e.g., first_name, company_name, amount_saved, cta_text, industry, etc.). Each project stores a table of placeholders (Add / Edit / Delete). These variables become available inside the Visual Editor.

Recommended conventions

  • Use lowercase, snake_case: first_name, company_name, local_offer.
  • For images, store a full URL. For colors, use hex (e.g., #1E90FF).
  • Only add variables you actually plan to use in Deploy experiences.

Step 4 — Build Your Personalized Deploy (Visual Editor)

  1. Open your Deploy experience in the Visual Editor.
  2. Place your cursor in Text / HTML / WYSIWYG / CSS where you want personalization.
  3. Insert a variable using or pick from Available Variables.

What you’ll see in the editor

  • Typing )
    4-1
    Clean editor baseline (before inserting variables)
    6-1

    Behaviour & Limits

    Behaviour and Limits are defined as per plan. Please refer Convert’s pricing page to understand the limits for respective plans.

     

    FAQs

    Q: Can I test personalizations on a Single-Page App (SPA)?
     Yes. The Convert script supports SPA triggers, but if you use a framework like Angular and see route/URL changes without reloads, make sure polling is triggered appropriately.

    Q: I don’t see the Visual Editor’s contextual menu/some UI won’t load.

    If your browser blocks third-party cookies, VE UI elements may not appear. Disable the browser’s “Block third-party cookies” or allowlist Convert domains.

    Q: Will personalization affect how my analytics receive experiment names?

    If Data Anonymization is enabled, experiment/variation names are replaced with IDs in the client-side JavaScript and any tools you integrate, which improves privacy. 

    Q: Can I send Convert data to my analytics tool alongside personalization?

    Yes. Use the real-time data objects (convert.currentData / convert.historicalData) to forward experiment context to your tools.

    Troubleshooting

    • CSV won’t upload
      • Re-export as CSV (comma-separated) from Excel/Google Sheets/LibreOffice.
      • Ensure that the first column is Visitor ID & the first row contains variable keys (headers).
    • Unknown variable warnings in VE
      • The variable key must exist in your project’s placeholders and match exactly.
      • Use the Available Variables list or type {{ to see suggestions.
    • Changes only reachable via VE Browse Mode don’t preview
      • Edit via variation code instead for those specific changes.
    • SPA page state not updating
      • Trigger Convert polling on route changes.

    Security, Privacy & Consent

    • Use only the data you’re allowed to process. If you insert personal data (names, company fields, etc.), ensure you have a lawful basis and update your privacy notices as needed.
    • Consent: If your personalization sets or relies on cookies/trackers, ensure tags fire after consent is gathered using your CMP.
    • Anonymization: Consider enabling Data Anonymization for experiment metadata sent to third-party tools.