Multi-Site Marketing Without the Busywork: Share Segments and Campaigns Across Sites

Multi-site marketing has a busywork problem. Whether you run regional storefronts, a portfolio of sub-brands, separate sites per location, or a roster of client accounts, the same work gets rebuilt over and over. The same cart abandoner segment, defined on the US store and again on the UK store. The same seasonal campaign, recreated by hand across six sub-brands. It works, right until someone edits one copy and forgets the other five.

Aimtell removes that duplication with shared segments and shared campaigns. Build it once, tick the sites you want it on, and every copy stays linked, so a single edit updates all of them. It is a checkbox and a dropdown in the dashboard, not a project. This guide covers how managing campaigns across multiple sites works, how to centralize campaign reporting so you can read one site or the whole portfolio from the same screen, how it pairs with repeating campaigns to automate recurring sends, and where the API fits if you would rather script the whole thing.

The Real Cost of Rebuilding the Same Campaign on Every Site

Running marketing across multiple sites gets expensive in three ways, and only the first one is obvious.

• Setup time scales linearly. A segment that takes fifteen minutes to define costs you an hour and a half across six sites. Every new campaign repeats the tax.
• Copies drift silently. This is the one that actually hurts. Someone tightens the cart abandoner window from 24 hours to 6 on the flagship site. The five regional copies keep the old definition. Nobody notices for a quarter, and your regional numbers quietly stop being comparable to each other.
• Reporting fragments. When the same campaign exists as six unrelated campaigns, there is no single number for how it performed. You export six result sets and add them up in a spreadsheet, every time someone asks.

Sharing solves all three, because there is only ever one thing to maintain and one screen to read the combined numbers from.

What Sharing Actually Does

Sharing creates a linked copy of your segment or campaign on each site you select. The copies are not snapshots. They stay tied together, so any edit applies everywhere automatically. Usefully, it does not matter which copy you edit. Change the one on your UK site and the change lands on every other linked site too, so nobody has to remember which site was the original.

At the same time, the copies are real segments and real campaigns living on their own sites. They evaluate against that site's own push subscribers, they send from that site, and their results are recorded against that site. That is what makes the model useful: one definition to maintain, but genuinely per-site audiences and per-site reporting underneath, which you can then roll up into a combined view whenever you want it.

Sharing a Segment: A Checkbox and a Dropdown

Segments come first, because a shared campaign needs a shared segment to target. If you have already built the segment you want (our guide to building high converting subscriber segments covers that part), sharing it takes about ten seconds:

1. Go to Segments and tick the checkbox next to the segment you want to share.
2. Open the Options dropdown and choose Share Segment.
3. A modal lists every website on your account with a checkbox beside each. Tick the sites you want, or use the checkbox in the header row to select all of them at once.
4. Click Save.

That is the whole flow. A matching segment is created on each site you selected. Give it a little time to fill in: depending on the size of the segment and how many sites you shared it with, the subscriber counts populate over the next few hours rather than instantly. The full walkthrough with screenshots lives in our Shared Segments help doc.

Sharing a Campaign: The Same Two Clicks

Once the segment is shared, the campaign works identically. From Manual, Triggered or RSS notifications, tick the checkbox next to your campaign, open Options, and choose Share Campaign. The same site list appears, and you tick the sites you want it on.

Two small touches worth knowing about in that modal. Sites that already have the campaign are grayed out and locked, so you cannot accidentally double-share and you can always see at a glance where a campaign already lives. And the header checkbox selects every site at once, which is the normal case when you are rolling something out across a whole portfolio.

A copy is created on each site, pointed at that site's copy of the shared segment. From here on, editing the campaign anywhere updates it everywhere. Our Shared Campaigns help doc has the annotated screenshots.

Centralize Campaign Reporting: One Site or All of Them

This is the part that tends to sell the feature. Open View Results on a shared campaign and you get a toggle at the top of the results screen:

• Current Site shows just this site's numbers, which is what a regional manager or an individual client cares about.
• All Sites (Shared Campaign) sums sent, delivered, bounced, clicked and conversion counts across every site the campaign is on, returned as one day by day breakdown.

Same screen, same campaign, one click between the two views. You are not exporting anything or reconciling spreadsheets, and because both views come from the same underlying campaign, the portfolio number and the per-site numbers always agree. Shared segments have the matching toggle on their own results screen, labelled All Sites (Shared Segment), so you can see the combined size of an audience across your whole portfolio as well as per site.

The toggle only appears on campaigns that are actually shared, so it stays out of the way on everything else. More detail in the campaign results help doc.

Pair It With Repeating Campaigns

Sharing gets considerably more useful when you combine it with the Repeat Campaign setting on a manual campaign. In the campaign's optional settings, flip Repeat Campaign to True and pick daily, weekly or monthly.

Share a campaign that has repeat turned on and the schedule travels with it, so every site in the group runs the same recurring send on the same cadence. A weekly new arrivals push now goes out across all six sub-brands, every week, from one campaign that you set up once.

The maintenance story is the real win here. Changing that weekly campaign's copy, image, link or cadence is a single edit that propagates to every site before the next run, rather than six edits you have to make before Monday. And you still get the per-site and combined numbers from the same results toggle, so you can see whether the weekly send is pulling its weight across the portfolio or just on the flagship. The other optional settings are documented in the manual campaign settings help doc.

Three Multi-Site Setups Where This Pays Off

1. A Multi-Region Retail Brand

One brand, separate storefronts for the US, Canada, UK and Australia, each its own site so subscribers, tracking and send times stay regional. The audience definitions, though, are identical everywhere: cart abandoners, high value repeat buyers, browse abandoners on a given category.

Share those segments once and every region inherits the same definition. When you tighten the cart abandonment window, all four regions move together instead of drifting apart. Regional teams still own their own results and read them on the Current Site view, while the brand team reads All Sites for the global picture.

2. An Agency Managing a Client Roster

You have a welcome sequence and a cart recovery campaign that you know work, and a new client every month who needs both. Rebuilding them by hand is billable time spent on data entry, and it is where inconsistency creeps in.

Build the proven campaign once on a template site, share the segment, then share the campaign to each client site. Rolling out an improvement you learned on one account becomes a single edit rather than a ticket per client. Each client still gets clean, isolated reporting on their own site, which is what ends up in their monthly report.

3. A Retailer with Sub-Brands on Separate Sites

A portfolio of sub-brands, each on its own domain and its own Aimtell site, all running the same seasonal promotion at the same time. The hard part is not the campaign, it is launching it everywhere at once and then reporting on it as one promotion.

Share the campaign across the portfolio and it launches from one place. Then flip the results toggle to All Sites and you have portfolio wide sent, clicked and conversion totals, day by day, without exporting anything. That is the number the person who approved the promotion actually asked for.

Two Things to Know Before You Share

There are exactly two rules, and between them they explain almost every sharing error:

1. The campaign must target exactly one segment. Campaigns targeting multiple segments cannot be shared, because there is no unambiguous way to map that onto another site.
2. That segment must already be shared with every site you want the campaign on. This is why segments come first. The copied campaign needs something to target when it lands.

A small set of segment conditions also cannot be shared, because they reference data that only exists on one site: Exists In Segment, Does Not Exist In Segment, Manual Campaign Clicked, Triggered Campaign Clicked and RSS Campaign Clicked. The first two point at another segment by ID and the last three point at a specific campaign by ID, and neither reference survives the trip to a different site. If you need something close to these, rebuild the condition from the underlying subscriber attributes or events instead, since those are tracked per site and travel fine.

Removing or Deleting a Shared Campaign

To take a campaign off one site, go to that site and delete the campaign there. Every other site in the group carries on unaffected. To delete the campaign everywhere, delete it and confirm the option to remove all shared copies.

One handy trick: if you want a site to keep the campaign but stop it from being linked, duplicate it first from the Options menu. The duplicate keeps all the campaign details as a starting point but is a standalone campaign, so you can then delete the shared copy and edit the duplicate freely.

Prefer to Automate It? There Is a Full API

Everything above is available through the Aimtell API, which is worth knowing about if you onboard sites regularly and would rather not click through the dashboard each time. The API and the dashboard drive the same mechanism, so campaigns shared either way behave identically.

The flow mirrors the UI: share the segment, then share the campaign, passing the site IDs you want.

curl -XPOST "https://api.aimtell.com/prod/campaign/98765/shared" \
     -H "X-Authorization-Api-Key: YOUR_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{ "sites": [456, 457] }'

Sites already in the group are skipped rather than duplicated, which is the API equivalent of those grayed out checkboxes, and it means you can safely run the same call from a provisioning script every time you add a site. On the reporting side, adding includeShared=1 to a results request returns the same combined totals as the All Sites toggle:

curl "https://api.aimtell.com/prod/campaign/98765/results
     ?startDate=01/01/2026&endDate=01/31/2026&includeShared=1" \
     -H "X-Authorization-Api-Key: YOUR_API_KEY"

Leave includeShared off and you get that site's own numbers, exactly like the Current Site view. Note that combined results are available for manual and triggered campaigns today. RSS campaigns can be shared, but for now you would pull each site's results separately.

Every endpoint involved is fully documented:

Generate an API key in the dashboard under Settings > API Key, and browse the complete reference at developers.aimtell.com.

Build It Once, Run It Everywhere

If you manage push notifications for more than one site, the duplication is not just wasted setup time. It is the drift between copies that nobody catches, and the fragmented reporting that makes the portfolio impossible to see. Shared segments and shared campaigns fix both, and the whole thing is a couple of checkboxes in the dashboard.

Ready to try it? Start a free Aimtell trial, browse the full feature set, or get in touch if you want help mapping your site structure onto shared segments before you roll it out.