Copy the provider questions
Use these questions when discussing browser extension installs for a specific store listing. Ask for answers about your product and proposed campaign. Record the supporting report, policy reference or method description beside each answer.
The questionnaire is open here without an email form. Copy it into your message or working document. Leave a point under “Not established” when the reply still needs a fact or confirmation.
EXTENSION INSTALL PROVIDER QUESTIONS
Extension / store URL or ID / version: ____
Provider / contact / date: ____
STORE POLICY AND USER CHOICE
- Which store policy applies to the proposed method?
- What will users see before installation, and how do they choose to install?
- Which store rules govern installs, ratings and reviews, and how will compliance be checked?
Answer: ____
Evidence or policy reference: ____
Not established: ____
SOURCES AND DISTRIBUTION
- Where will people encounter the extension?
- What path takes them from that placement to the store listing?
- What can we review to check the source and pre-install information?
Answer: ____
Evidence or method description: ____
Not established: ____
TARGETING
- Which stores, browsers and countries are available for this listing?
- What exclusions and targeting limits will be written into the offer?
- Which evidence can confirm the agreed targeting?
Answer: ____
Evidence or report: ____
Not established: ____
PACING AND CHANGES
- How will the volume be distributed across the campaign dates?
- Who approves changes to the daily plan or scope?
- Who can pause the campaign, and how do we contact them?
Answer: ____
Evidence or agreed schedule: ____
Not established: ____
MEASUREMENT
- What counts as an install, including repeat or returning installations?
- Which report, baseline, period and filters will we use?
- If active use is required, what useful action and report will measure it?
Answer: ____
Evidence or export: ____
Not established: ____
STOP CONDITIONS
- How will a campaign be stopped if an unagreed acquisition method is found, and which other issues trigger a pause?
- Who investigates, and what records are kept?
- Who can approve a restart, and what must be checked first?
Answer: ____
Evidence or agreed rule: ____
Not established: ____
Keep the completed questionnaire with the proposal. Use the extension install pilot plan to turn accepted answers into campaign settings, a review date and a decision rule.
Check the policy and the installation choice
Identify the store before reviewing the method. Ask the provider to describe what happens from the first promotion to installation, including what the user is asked to do. The description should let you check the proposed flow against the policy for that store.
For Chrome, the deceptive installation policy requires transparent promotion and clear expectations about installing an extension. Ask to see the message and installation prompt together so you can review what a person is being offered.
Check the proposed acquisition method against Chrome Web Store’s Spam and Abuse policy. Do not approve a method that conflicts with the store’s rules. User consent or client approval does not override those rules.
Ask where users come from
A useful source description explains where people encounter the offer and how they reach your store listing. Ask for the type of placement, the steps in the path and the information shown before installation. Put those details in the campaign agreement.
If the reply promises “real users”, ask who is counted and what evidence supports that description. Request the promotion message or a description of the agreed path to the store listing.
The service page’s questions to settle before a campaign cover distribution, user information and evidence. Use them when the proposal describes an install total but leaves the acquisition method unclear.
Confirm targeting for your listing
Send the exact store URL or extension ID, browser and requested countries. For work across several stores, ask for the scope and report for each listing. Keep those replies separate so a later result can be matched to the right product.
Have the provider identify the countries and exclusions included in the offer. Ask which report can check those settings and whether its country or browser coverage matches the requested campaign. Confirm availability for your listing before treating a targeting preference as an agreed condition.
Record alternatives as alternatives. If the provider proposes a wider geography or another browser, have the person responsible for the product decide whether that revised scope still serves the campaign goal.
Agree pacing and control of changes
Ask for the total volume and its distribution across the campaign dates. Include the time zone, any daily plan or limit, and the person responsible for coordinating changes. This gives the product owner a schedule to review alongside releases and store-listing updates.
Agree how a change is requested, approved and recorded. A different country mix or delivery window should leave a dated update in the plan. Give the provider a named contact who can make the decision, rather than leaving approval to an informal message chain.
Ask who can pause the work if the listing becomes unavailable or the first-use flow breaks. Keep that contact and the pause rule with the schedule so the people running the campaign can act on it.
Define installs and active use separately
Choose the exact install measure and its source. Ask how it counts repeats and returning installations. Save the starting value, date, report period and filters, then agree which export or record the provider will supply for review.
Google’s Chrome Web Store metrics documentation says daily install counts include new and returning users. It also explains that the Users statistic captures installations rather than activity. A promise stated as “users” needs the report definition before you can assess it.
If your goal requires active use, name a useful action inside the extension and the period in which it should occur. Ask who can measure it and what unit is counted. Record a missing activity measure as “not measured” and review the campaign against the measures actually agreed.
When the unresolved issue concerns the listing, onboarding or first useful action, discuss extension growth. That product work helps define what you want a newly acquired user to do.
Set conditions for pausing and stopping
Agree the triggers before delivery starts. Stop a campaign if it uses an acquisition method that was not agreed or does not comply with the store’s rules. Useful questions include what happens if the listing is unavailable, the product cannot complete its useful action or required reporting is missing. Write the trigger and the person who decides the next step.
Ask what records will be kept during a pause, how the affected period will be reviewed and how the remaining scope will be handled. Agree what must be checked before restarting. Keep the review tied to the original listing, dates and measure.
At the review date, compare the evidence with the accepted answers in the questionnaire. Decide whether to continue, revise the scope, fix the product or stop. Record the next action and its owner in the pilot plan.
Discuss the method with Extcorp
Extcorp offers extension install campaigns through advertising.
Extcorp reviews install-campaign requests for Chrome Web Store, Microsoft Edge Add-ons and Mozilla Add-ons. Start with your contact and a short question about the extension. Add the store link or ID when it is ready.
Price and test are on request. Discuss the browser, countries, period and install measure. Review the result before deciding on a paid campaign.