Start with one partner question
Leave a contact, name the service and describe the client’s task. The filled two-website brief shows how to keep separate projects and missing information clear; the blank structure is optional for first contact.
Use the first discussion to agree who handles evidence and client wording. Sending a report and the client accepting its contents are separate steps. Identify who keeps unresolved items open and who confirms their closure before treating a handover as accepted.
Ask about partner terms. Detailed reporting, recipients and confidentiality can be settled for the selected service.
Roles in a White Label project
The partner typically manages the client relationship, commercial agreement and brand communication. Extcorp is responsible for the operational work and reporting agreed in the project brief.
Partner responsibilities
Manage the end-client relationship, approve the work, collect required information and control the brand and communication model.
Extcorp responsibilities
Check feasibility, complete the agreed work, report constraints and provide the agreed status or reporting data.
Shared decisions
Agree how changes, missing inputs, platform issues, verification questions and client-sensitive decisions are handled.
Services available for resale
- Similarweb Traffic, Semrush Traffic and GA4 Traffic, each with its own reporting source and metric definitions.
- Chrome, Microsoft Edge and Firefox extension install acquisition where available.
- Extension store, onboarding and product-growth review.
- Browser extension development, adaptation and maintenance.
- Extension monetization assessment and scoped implementation.
- Confidential discussion of established browser extensions with active users.
What to send first
Name the service your client needs and describe one project. Add the website URL or extension link if available, who should handle client communication, and any reporting or confidentiality requirements. Mark undecided details for discussion.
Agree what the client will receive
Describe the report or handover your client expects before agreeing the project. Specify who may see the underlying evidence and who approves the wording sent to the client. A branded presentation still needs the original metric definitions, dates and unresolved questions.
| Decision | Question to agree |
|---|---|
| Project inputs | Who collects the website or extension details, confirms permitted access and follows up on missing information? |
| Scope and changes | Who approves the brief and later changes before they affect delivery or client wording? |
| Evidence to share | Which source, report, capture date and limitations may be shown under the agreed confidentiality terms? |
| Client follow-up | Who answers the end client, receives open issues and confirms that a question has been resolved? |
Examples of a report that still needs evidence
In an illustrative traffic report, the service could be Semrush Traffic Service, with Traffic Analytics, the exact metric, reporting dates and country/device filters recorded. If the source export has not arrived, mark the result “awaiting source data”. Use “not measured” only when the measurement was not made. Neither status establishes zero traffic, completed delivery or verified growth. The traffic comparison page explains why the platform and report must stay visible.
An illustrative development handover could name the browser and build, the behavior tested and a remaining update check. Mark that check as “not checked” and name the person who will complete it. Passing the recorded behavior does not close the open item or establish store approval; development scope should identify who owns acceptance and release.
Keep a dated correction or clarification attached to the affected report item, so the recipient can distinguish the original observation from a later update. Agree who tells the client when a source or interpretation changes.
Tell us the arrangement you need, including branding, access and communication boundaries. Agree the report format, any integration work and response arrangements for the selected service.
A brief for more than one website
If your agency has several website projects, list each website and requested service separately. Two services for the same site need two records so their reports and measures stay distinct. You can use the fields below to prepare a discussion; completing them is optional before first contact.
Write the shared instructions once: your partner contact, who may receive information intended for the client, and any branding or confidentiality requirements. Note exceptions against the affected website.
Fields to repeat for each website and service
Copy these field names into a message or spreadsheet and fill in what you already know:
Download the optional multi-site brief (.txt)
| Field | Details to include |
|---|---|
| Website / client reference | The domain or an agreed reference if the client identity is confidential. |
| Requested service and question | Similarweb Traffic, Semrush Traffic or GA4 Traffic, and what the client wants to understand or change. |
| Report and exact metric | The report, the GA4 property where relevant, and the full metric name and unit. |
| Dates and filters | The period, time zone and relevant country, device or source filters. |
| Requested settings | Known preferences for the campaign. Availability still needs review. |
| Data and missing information | Available reports or observations, the information still needed and who can provide it. |
| Permitted recipients | Who may receive the source reports and who may receive the client report. |
Leave unknown quantities empty and record the missing information in its own field. Preserve the difference between awaiting source data, not measured and not checked. Keep Similarweb estimates, Semrush estimates and GA4 measurements on separate lines; adding them together does not produce a verified audience total.
This worksheet helps explain the request. Feasibility, delivery, report format, frequency and any integrations are agreed for the selected services. To discuss partner terms, a contact and a short question are enough to start; website details can follow.
A filled brief for two websites
This is a teaching example for the reserved domains example.com (client A) and example.org (client B). The instructions and data states are fictional. They illustrate a request for discussion, with no agreed price, volume, reporting service or delivery commitment.
Shared instructions: the agency account manager handles client communication and approves client-facing wording. The agency analyst collects reports. The proposed format is a table under the agency’s brand, with the original source, filters and limitations retained. Access and permission to share source reports still need the clients’ approval. Extcorp is asked to review feasibility and proposed terms before any work is agreed.
| Website and request | Report, metric and settings | Missing information and who resolves it |
|---|---|---|
| A: example.com. Similarweb Traffic. Discuss a US desktop campaign and how to review the external estimate. | Website Performance; Total Visits. September 2026 baseline; United States; Desktop; all channels. Fixed EST. | Estimate unavailable in this fictional scenario. Value blank. The agency analyst saves the provider's message and confirms available coverage; no result date is assumed. |
| A: example.com. Semrush Traffic. Keep a separate Semrush observation for the same proposed project. | Traffic & Market → Traffic Analytics; Visits. September 2026 baseline; United States; Desktop; all channels. | Awaiting source export. Value blank. The agency analyst supplies the export, capture time, data-status notice and report time zone; Organic Rankings is not a substitute. |
| B: example.org. GA4 Traffic. Discuss sessions from Germany on mobile for the client's own site. | Traffic acquisition; Sessions. September 1 to 30, 2026 baseline; Country = Germany; Device category = mobile; all session channels; proposed web-only scope. | Not checked. Value blank. Client B's analytics owner confirms the property, web stream, reporting time zone and permitted access before the analyst obtains a report. |
Here, Total Visits is Similarweb’s estimated website visits; Visits is Semrush Traffic Analytics’ estimate across channels; Sessions is GA4’s count under its session rules. A site’s users, its organic-search estimate and the three services’ totals cannot replace those fields. The filled platform comparison explains the remaining scope and time differences.
The baseline month above is a requested reference period. Campaign start, pace and volume are still undecided. The account manager asks each client for those preferences; Extcorp reviews availability separately for each service. The two sites have different country and device requests, so their rows should stay distinct even within one agency report.
“Unavailable estimate”, “awaiting export” and “not checked” describe different gaps. “Not measured” would apply if the required measurement was never collected. Keep the value blank and assign the next question to a named role; none of these states means zero or completed delivery. For this example, report recipients and sharing rights remain unapproved, and the agency must resolve them before distributing source data.
Use the existing blank brief for your projects, or send a short partner question. A complete worksheet is optional. Definitions follow the linked platform comparison, checked October 13, 2026.
How a partnership starts
- Check the fit. Discuss client profile, services, platforms, GEOs, expected volume and operating constraints.
- Define confidentiality and roles. Agree NDA needs, brand use, direct contact restrictions and responsibility boundaries.
- Submit a real project. Include the inputs required by the selected service.
- Agree delivery and reporting. Set pacing, checkpoints, report fields and escalation paths.
- Review the first project. Evaluate communication, evidence and operational fit before adding projects or volume.
Independent service provider status
White-label delivery does not turn Extcorp or the partner into an official representative of Similarweb, Semrush, Google, Chrome Web Store, Microsoft Edge, Mozilla or Firefox. Client-facing material should preserve the same measurement distinctions and independent-provider disclosure used throughout this site.