To avoid treating one creator's accounts as separate prospects, give the creator one internal ID and attach each confirmed profile to it. Keep representation and campaign contact routes in separate records. A shared agency email can connect several creators without making them the same person. Deduplicate the people first, then review the messages you plan to send.
Keep three matching decisions separate
An email address tells you where a message goes. It does not establish who owns every profile that lists it. Microsoft's shared-mailbox documentation explains that several people can use one mailbox and send from it with the right permissions.
Use these three decisions in your worksheet:
| Decision | Question | Record to keep |
|---|---|---|
| Creator identity | Do these profiles belong to the same creator? | Creator ID with linked profiles |
| Representation | Who handles this creator's business inquiries? | Representative or agency linked to the creator |
| Campaign contact | Where should this campaign's conversation go? | Campaign, creator, chosen route and conversation owner |
These are recommended recordkeeping rules. Social platforms do not prescribe this worksheet.
The separation also helps people manage relationships. Modash's article on influencer relationships recommends building relationships with talent managers and discusses assigning creators a single team contact. Your records should preserve both the creator relationship and the representative relationship.
Decide which profiles belong together
Start with the source profiles, before sorting by email. Keep the original profile URL and assign a temporary row ID so a later merge does not erase where the record came from.
Use this review order:
- Same profile. Two rows pointing to the same confirmed account are duplicate profile records. Keep one profile record and combine its source notes.
- Creator-owned connection. A creator's established website links to both accounts, or the established account identifies the other as theirs. Review the links and any conflicting details before assigning one creator ID.
- Possible match. Similar handles, names, portraits or content suggest a candidate for review. Keep the records separate until you have stronger evidence.
- Shared contact only. The same agency domain, manager name or inbox is evidence about the contact relationship. It is insufficient evidence for a creator merge.
For uncertain links, use the checks in verify that a contact page belongs to the creator. Avoid a universal similarity score that lets several weak clues outweigh contradictory ownership evidence.
A joint account needs an explicit decision. If two creators run a shared channel, record the joint project and its relationship to each person. Do not merge the people into one individual record because they share that channel.
Copy this deduplication worksheet
Keep one row per observed profile while reviewing. Repeat a confirmed creator ID across that creator's profiles. Repeated IDs are expected in this sheet.
| Field | What to enter |
|---|---|
| Source row ID | Original import or research row reference |
| Profile | Platform and full profile URL |
| Creator ID | Your stable internal identifier, independent of email |
| Match status | Confirmed, possible match or separate |
| Match evidence | Source URL, observed connection and review date |
| Representation | Agency or representative, scope and source |
| Contact route ID | Identifier for the business inbox or contact form |
| Route scope | Creator-specific, shared representation or unknown |
| Campaign assignment | Campaign ID, selected route and team owner |
| Merge decision | Surviving creator ID, reviewer and reason |
Preserve the address as supplied. Remove accidental surrounding spaces when preparing a comparison field, but do not strip dots, plus suffixes or other characters to manufacture a match. Route matching and creator matching remain separate decisions.
For source notes your next teammate can check, follow record where each creator email came from.
Shared-inbox counterexamples
The following worksheet is hypothetical. Names, IDs and contact routes are invented; inbox labels are identifiers rather than published addresses.
| Observed records | Evidence | Decision |
|---|---|---|
| Mira's Instagram and YouTube | Her established website links to both | Assign creator C01 to both profiles |
| Mira and Leon | Separate creator pages list agency inbox R01 | Keep C01 and C02; link both to R01 |
| Mira's old and new contact routes | Her current business page names a new representative | Keep C01; mark the old route superseded for new outreach |
| Two accounts named Mira Studio | Similar handles, no ownership connection | Leave as possible matches |
| Mira and Leon's joint channel | Their established pages identify it as a joint project | Link the project to both creators; keep their IDs separate |
For a hypothetical autumn campaign, Mira's two profiles become one prospect assignment. Leon remains a second prospect even though R01 serves both people.
Now review the recipient queue. Two valid creator assignments can still produce repetitive emails to the same agency. Let one team owner decide whether to send a combined inquiry naming both creators or maintain separate, clearly named conversations. Follow any business-inquiry instructions the representative publishes.
Do not discard Leon's assignment merely because R01 already appears in the queue. That would remove a person when the duplicate was only a destination.
Check your CRM's import behavior
Before importing shared-inbox rows, read how your CRM matches contacts. HubSpot documents automatic contact deduplication by email, including blocking manual creation of another contact with an existing email address.
In a system with that behavior, filling each creator's primary email field with the same agency address can collapse information you meant to keep separate. Your spreadsheet's creator IDs alone do not prove the import will preserve that distinction.
Ask the CRM administrator how to store a shared representative and link the creator records to it. If the available setup cannot express that relationship, keep a separate creator register until an appropriate mapping exists. Do not invent alternate email spellings to force separate contacts through an import.
Test the mapping with hypothetical rows before loading your researched list. Inspect both the resulting creator records and the outbound recipient list.
Review the next send after merging
A confirmed identity match does not select a contact route or authorize a message. YouTube's business-inquiry help says an address is visible only when the channel owner has supplied one. That documents availability; it does not identify everyone behind the inbox.
Limit outreach to creator-welcomed business inquiries where applicable rules permit the message. Use the business-contact boundary guide before treating a public address as usable.
After a merge, check queued messages, existing conversations and any contact restrictions attached to either record. Pause conflicting assignments for review. Keep the surviving creator ID, the retired row references and the reason together so a teammate can understand or reverse an incorrect match.
Start with the repeated addresses in your next campaign list. For each group, decide whether it represents one creator, several creators sharing representation, or an unresolved match before releasing any messages.
