Personyze is an automation hub where your data turns into personalization actions. It supports 70+ metrics, broadly:

• IP intelligence: Geo (continent→city) and weather variables.
• Referral: Source (site, ad campaign, search keyword, etc.).
• Behavior: Pages visited/not visited, landing page, time on site, popular pages, hovers, and more.
• Third-party integrated: Social, CRM/CDP, and any external/offline data via feed or upload.
• Dynamic / grabbed data: Values extracted from page, URL params, cookies, meta tags, hidden divs (e.g., cart value).
• Ranked interests: Built from interactions with products/content (when using recommendations).

Yes. Personyze integrates with ESPs, analytics tools, CMS/eCommerce, CRMs, Facebook, HubSpot, and more. If data can be shared via file/feed—or an API/webhook exists—Personyze can use it. Popular platforms (e.g., HubSpot, Segment, Salesforce) have turnkey connectors.

Yes. Personyze integrates with Google Analytics by default and works with most analytics tools. It also includes built-in reporting.

Yes. Data is used only for analysis, personalization, and optimization of your properties. We do not sell or share it with third parties.

Yes. Enable the GDPR-compliant mode in your account settings. (See Personyze GDPR resources for details.)

Yes. Upload/synchronize via CSV, feeds, or secure file transfer and use it for targeting and personalization.

Yes—via direct connectors (e.g., Segment, Tealium, Zeotap), reverse-ETL, APIs/webhooks, or secure file transfers. CDP data becomes immediately usable for on-site targeting.

First-party cookies to recognize returning users, honor preferences, and measure performance. No personal data is stored in cookies.

Personyze ingests real-time streams (APIs, webhooks, CDPs), client-side tags, and batch uploads (CSV/SFTP). Profiles are stitched by identifiers (user ID, hashed email, device ID, custom keys) to unify online/offline data.

Yes. You can delay tracking until consent, respect Do-Not-Track, and map consent states to features (e.g., disable recommendations until “performance” consent).

By default on AWS, with encryption in transit and at rest. Enterprise plans can request region configuration.

Aggregated analytics follow plan defaults. Identifiable user-level data can be shortened or purged via retention policies or upon request.

Yes. SSO (SAML/OIDC) and granular roles/permissions are available on higher tiers.

The tag loads async, uses CDN/edge caching, and is optimized to keep render blocking near zero. Typical added latency is a few ms.

Yes—enable SPA tracking and trigger route-change events so targeting and rendering update without full page loads.

Yes. Add the tracking code and Personyze can personalize any site that runs in a browser.

Yes. Lightweight iOS and Android SDKs enable in-app personalization.

Follow the iOS/Android quick-start: initialize the SDK, set the user ID, and send events. This enables flexible in-app personalization.

Yes. In Account Settings → General → Tracker Settings, add your subdomains. You can track any domain you control.

Yes. Enable Single Page Application Tracking in Account Settings → General → Tracker Settings.

Yes. Use the tag-manager version shown by default in Account Settings → General → Tracker Settings. Don’t mix header and TM versions together.

With monthly packages, yes—upgrade, downgrade, or cancel anytime.

Yes—consultants, agencies, referrers, platforms, and more. To discuss a partnership, contact Support.

Extra usage is billed in blocks per your plan and charged proportionally to actual overage (e.g., if 1M extra is $100 and you exceed by 200k, you pay $20).

Credit card, wire/invoice, or PayPal. For invoices, contact Billing.

Typically we operate under the user agreement, but we can sign a mutual NDA upon request.

Since 2008, with continuous platform evolution.

Page Views are calls to Personyze to decide what content to show—on web pages, in embedded email recommendations, in apps, or via API. If you use Personyze only on your website, charged views mirror your actual page views (where the tag runs).

Targeted visual/content changes for a specific audience on selected pages to match persuasion or user flow (e.g., Spanish experience + local recs for Spanish-browser users in Mexico).

Yes. Cross-domain goal tracking, testing, and targeting are supported out of the box—use any number of sites.

Yes—affordable and scalable for marketing agencies. Schedule a meeting to learn more.

1. Broadcasted via Personyze (Amazon SES): a quota is included; overage is billed per plan.
2. Embedded recommendations in your emails: each view counts as a page view toward your quota.

Each successful response that requires decisioning (e.g., recommendations, targeting) counts as a page view for pricing.

99.99% availability. Support SLAs vary by plan; enterprise includes priority response and escalation.

Yes—template porting, audience mapping, and measurement-parity checks are included in onboarding for eligible plans.

Reasonable defaults apply; enterprise plans can raise ceilings. Retries and backoff strategies are supported.

Yes—available under NDA for security review.

We support DSAR workflows (access, delete, opt-out of sale/share) with admin tools and APIs to fulfill requests.