Merging and Managing Subscribers Across Multiple Domains

Learn more about how you can track subscribers across domains and how you can create a better subscription experience

Available for customers on iZooto's Enterprise Plan

We often come across cases where a business with more than 1 website, needs to set up a subscription experience such that users across two websites are asked to subscribe only once or either of the domain.

Implementation

Master Pixel [Available only on Enterprise Plan]

Such implementations where subscriptions across multiple websites are managed under one account are done using iZooto's Master Pixel.

Consider 2 domains - https://www.roomno368.com and https://www.roomno.378.com. If a user is subscribed on https://www.roomno368.com, the same user would not be asked to subscribe on the second domain (https://www.roomno378.com).

Also, the domain on which the user subscribes for notification is tagged against them to ensure that you can create an audience and target subscribers of a specific domain.

You can segment user who subscribed to a specific domain using Audience Builder

You can segment user who subscribed to a specific domain using Audience Builder

Subscriber Management

  • We start with putting together the list of all the websites (domains) for which we want to merge subscribers.
  • One specific domain is identified as the master domain and rest all the domains are considered as child domain.
  • Subscribers across all websites ( master domain + child domains ) are merged under the master domain.
  • You can segment your audience and track which subscriber belongs to which domain.

Maximum domains that can be merged

There are always practical limits to specific custom implementations. It is advised that is kept to less than 15. For more questions, drop a line on support@izooto.com

Merging and Managing Subscribers Across Multiple Domains


Learn more about how you can track subscribers across domains and how you can create a better subscription experience

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.