Forking campaigns shared across teams

The Tremendous API domain model previously had a notion of shared campaigns across teams (organizations).

When you create a new team, we provide the option to copy settings, campaigns, and users over from another team.

Confusingly, campaigns weren't actually copied over. Rather, the new team would have access to the same actual campaign resource. This meant that one campaign could be used across multiple teams.

This was problematic - modifying the campaign in one team would have unexpected impacts on others. Users complained about this over and over again.

Today, we've done a migration that splits those campaigns, so that campaigns are now 1:1 to a team. We did this by cloning campaigns that belonged to multiple teams. If a single campaign resource was shared across 5 teams, we've cloned that campaign into 5 copies, and assigned each one to one unique team.

Now, you can safely modify campaigns in one team, and be sure that they won't affect others.

How the API is affected

We returned shared campaigns in the GET /campaigns API call. But as a result of this cloning, some of these shared campaigns will have different IDs, since they are now unique records.

It's not a breaking change. Old campaign IDs will continue to work as expected in API calls, and there should be no changes required to active API integrations.

This only affects a handful of API clients. We will communicate directly with affected API clients to update campaign IDs, with a lengthy time window for any migrations required.

If you have questions, please contact us at [email protected].