The CC // naming convention is a campaign-name prefix that tells CreatorCommerce which impact.com campaigns to treat as co-branded program tiers. When you prefix an impact campaign with CC // — for example, CC // Ambassadors — every creator in that campaign is automatically mapped to the matching tier inside CreatorCommerce, with the right co-branded shop template, discount logic, and routing rules applied. This guide covers when to use the prefix, the priority logic CreatorCommerce applies when a creator is in multiple campaigns, and how to keep your campaign hygiene clean enough that every partner lands in exactly the tier you expect.
CreatorCommerce is a Shopify-native platform for co-branded creator storefronts that integrates directly with impact.com. The CC // prefix is the campaign-naming standard CreatorCommerce uses to make tier mapping deterministic — a small upfront convention that saves hours of remapping work later when a program scales past 100+ partners.
CC // naming convention: A campaign-name prefix that signals to CreatorCommerce which impact.com campaigns should be treated as co-branded program tiers. Campaigns prefixed with CC // are mapped 1:1 to CreatorCommerce tiers; campaigns without the prefix fall through a fallback priority order.
Why the CC // Prefix Exists
CreatorCommerce maps impact.com campaigns to its own creator tiers — this is how the platform decides which co-branded shop template, discount, and routing rules each partner gets. For brands running a single impact campaign per creator, this is straightforward. For brands running multiple campaigns where a single creator might appear in two or three (an Ambassador also enrolled in Holiday Gift Guide, for example), the platform needs a deterministic way to choose the primary campaign.
That's what the CC // prefix solves. By marking the campaign you want CreatorCommerce to treat as a creator's primary co-branded program, you remove the ambiguity. Every partner ends up in exactly the tier you expect, and any campaign overlaps stop creating routing surprises.
The prefix isn't required — the integration still works without it. But the routing logic falls back to a priority order, and that priority order is harder to predict at scale.
How to Apply the CC // Prefix
The setup is simple: prefix any impact.com campaign you want CreatorCommerce to treat as a co-branded program tier with CC // (note the spaces around the slashes). Here are typical campaign names that follow the convention:
CC // AmbassadorsCC // Holiday Gift GuideCC // Practitioner ProgramCC // VIP CreatorsCC // AffiliatesCC // Influencer Program
The text after CC // becomes the tier name inside CreatorCommerce. So CC // Ambassadors maps to a CreatorCommerce tier named “Ambassadors,” with whatever shop template, discount logic, and routing rules you've configured for that tier.
Campaigns without the CC // prefix still sync — the integration captures every partner in every relevant campaign. But for routing purposes, prefixed campaigns take priority.
The Priority Order CreatorCommerce Uses
When a creator is in multiple impact.com campaigns, CreatorCommerce uses this priority order to decide which campaign to treat as primary:
- Single campaign rule. If the creator is in only one campaign, that campaign is used. No ambiguity.
- Single CC // match. If the creator is in multiple campaigns and exactly one of them contains
CC //, that campaign wins. - Multiple CC // matches. If the creator is in multiple campaigns and more than one contains
CC //, CreatorCommerce uses the most recent matching campaign (based on campaign start date in impact). - No CC // match. If the creator is in multiple campaigns and none contain
CC //, CreatorCommerce uses the most recent campaign overall.
This order is intentional. The fastest path to deterministic routing is to use the prefix on exactly one campaign per creator — that gets every partner mapped via the second rule, which is the most predictable.
Worked Examples
Here's how the priority logic plays out in practice:
Example 1: A creator in one campaign
A creator is in CC // Ambassadors. They map to the Ambassadors tier in CreatorCommerce. (Single campaign rule — straightforward.)
Example 2: A creator in one CC // and one non-CC campaign
A creator is in CC // Ambassadors and Holiday 2026 Promo. They map to the Ambassadors tier. (Single CC // match — CC // wins over the non-prefixed campaign.)
Example 3: A creator in two CC // campaigns
A creator is in CC // Ambassadors (started Jan 2026) and CC // VIP Creators (started Apr 2026). They map to VIP Creators because it's the most recent. If you wanted them to stay in Ambassadors, remove them from VIP Creators in impact, or rename one of the campaigns to drop the prefix.
Example 4: A creator in two non-CC campaigns
A creator is in Q4 Affiliate Push (Oct 2026) and Spring Influencer Wave (Mar 2026). They map to Q4 Affiliate Push (most recent). To make this deterministic going forward, prefix one of the campaigns with CC //.
Best Practices for Campaign Hygiene
Most routing surprises come from campaign sprawl, not from the integration logic. A clean campaign structure in impact.com makes the integration nearly self-managing.
- Use the
CC //prefix on exactly one campaign per creator. This is the fastest path to deterministic routing. MultipleCC //campaigns on the same creator force the integration into the “most recent” fallback, which is harder to predict. - Keep tier-level campaign names stable. If a campaign is
CC // Ambassadorsfor the long term, don't rename it toCC // Ambassadors 2026for the new year — the tier mapping in CreatorCommerce will lose its history. Use end-date logic in impact instead. - Treat seasonal campaigns separately. A
CC // Holiday Gift Guidecampaign should be its own tier (or the same tier with seasonal content), not folded into the Ambassadors campaign. Cleaner separation makes downstream segmentation easier. - Audit before scaling past 100 partners. Once a program reaches 100+ partners, campaign hygiene compounds. Spend an hour cleaning up duplicate campaigns, retired tiers, and overlap before the program gets bigger — much easier than untangling at 1,000+.
- Document the convention internally. If multiple people on your team manage impact campaigns, write down the
CC //rule somewhere they'll see it. Onboarding a new affiliate manager and having them createCC//Ambassadors(no spaces) instead ofCC // Ambassadorsbreaks routing.
Common Mistakes to Avoid
A few patterns we've seen trip up brands during setup:
- Wrong spacing.
CC //requires the space afterCCand before the second slash.CC//Ambassadors,cc // Ambassadors, andCC: Ambassadorsare all treated as non-prefixed campaigns by the integration. - Multiple
CC //campaigns by accident. Cloning a campaign in impact often duplicates the prefix into the new campaign name. If you cloneCC // Ambassadorsto create a seasonal variant, the new one inherits the prefix — and now your creators are in twoCC //campaigns at once. Rename or remove the prefix as part of the clone. - Treating campaign names as throwaway. In impact's UI, campaign names are sometimes treated as internal labels that nobody looks at carefully. With the CreatorCommerce integration, the campaign name is the tier mapping. Rename casually and you change the integration's behavior.
- Forgetting to update tier configuration in CreatorCommerce. Adding a new
CC //campaign in impact doesn't automatically configure the corresponding tier in CreatorCommerce — you still need to set up the tier's shop template, discount logic, and routing rules inside CreatorCommerce.
For the full integration setup including credentials and the initial sync, see the Setting Up the Impact Integration help article.
Frequently Asked Questions
What is the CC // naming convention in impact.com?
The CC // naming convention is a campaign-name prefix that tells CreatorCommerce which impact.com campaigns should be treated as co-branded program tiers. For example, an impact campaign named CC // Ambassadors maps to the Ambassadors tier inside CreatorCommerce, with the right co-branded shop template, discount logic, and routing rules applied.
Do I have to use the CC // prefix?
No. The integration syncs creators from every relevant impact.com campaign whether or not the campaign uses the prefix. The prefix exists to make tier routing deterministic when a creator is in multiple campaigns. For brands with simple campaign structures (one campaign per creator), the prefix is optional. For brands with multiple campaigns per creator, the prefix is the cleanest way to control which campaign CreatorCommerce treats as primary.
What happens if a creator is in multiple impact.com campaigns?
CreatorCommerce uses a priority order: a single campaign always wins; if there's exactly one CC // campaign, that wins; if there are multiple CC // campaigns, the most recent one wins; if there are no CC // campaigns, the most recent campaign overall wins. For deterministic results, prefix exactly one campaign per creator.
Can I rename my impact.com campaigns after the integration is live?
Yes, but be careful. Renaming a campaign changes the tier mapping inside CreatorCommerce, which can shift creators into different shops or rules. If you need to rename a campaign, plan for the downstream tier reconfiguration in CreatorCommerce as part of the change.
Does the CC // prefix work on existing impact.com campaigns?
Yes. You can add the CC // prefix to existing campaigns in impact at any time — the next sync picks up the renamed campaign and applies the new mapping. For brands that already have an active program, adding the prefix retroactively is the cleanest way to migrate from “no prefix” routing to deterministic routing.
What's the difference between a CreatorCommerce tier and an impact.com campaign?
An impact.com campaign is a partner program inside impact — it groups partners and sets commission, attribution, and contract rules. A CreatorCommerce tier is a partner classification inside CreatorCommerce — it sets the co-branded shop template, discount logic, and routing rules. The CC // prefix is the bridge that maps impact campaigns to CreatorCommerce tiers 1:1, so partner data flows through cleanly.
Get Started
The CC // prefix takes minutes to apply and saves hours of routing remapping work as a program scales. If you're setting up the impact.com to CreatorCommerce integration, this is the convention to apply before the initial sync.
See how it works → Book a demo with CreatorCommerce
Related Articles
%201.png)
%201.png)
