Which Team Members Need to Be Involved in Activating BotRefund?

Activating BotRefund requires coordinating a few specific roles. Your ad manager or media buyer configures the integration settings and connects your ad accounts. A web developer or IT person adds the single script tag to your website. Finance or accounting sets up refund preferences and reviews the claims. Each role has clear responsibilities, and skipping one can delay or weaken the refund process.

Who needs to be involved?

Three teams typically share the activation work: marketing/advertising, web development, and finance. The exact split depends on your company structure, but the core tasks are the same.

The role of the ad manager or media buyer

This person manages the ad accounts that BotRefund will monitor. They need to provide access to Google Ads and Meta Ads accounts, review the free audit results, and approve the initial refund claims. They also ensure that tracking parameters (like GCLID and fbclid) are properly passed through the campaign URLs. In most cases, the ad manager is the main point of contact for BotRefund support.

The role of the web developer or IT team

BotRefund installs via a single JavaScript snippet, much like a Google Analytics tag or a Meta pixel. A developer adds this script to every page of your website, ideally in the section. If you use a tag manager (e.g., Google Tag Manager), they can deploy it there instead. The developer also verifies that the script loads correctly and does not conflict with other tags. No server-side changes or database access are needed.

The role of finance or accounting

Finance handles the business side. They set up how refunds should be processed—whether credits go back to the ad account or to a bank account. They also review the dispute logs that BotRefund generates and approve the submission of refund claims to Google and Meta. In larger teams, finance may coordinate with the ad manager to ensure the refunds are applied correctly.

Before activation: what each team should prepare

The ad manager should gather a list of all Google Ads and Meta Ads account IDs, confirm that auto-tagging is enabled, and check that GCLID and fbclid parameters appear in the final landing page URLs. The developer should verify they have edit access to the website header or to the tag manager container, and they should test the snippet in preview mode on a staging environment before pushing to production. Finance should collect the current billing contacts for each ad platform, decide whether refunds will be taken as account credits or as cash payouts, and confirm they have permission to approve dispute submissions.

Handoff checklist between teams

After the script is live, the developer sends a confirmation screenshot showing the snippet firing on all page types (home, product, checkout, thank‑you). The ad manager then connects the ad accounts in BotRefund and shares the audit link with finance. Finance reviews the audit summary, sets the refund preference (credit vs. payout), and signs off on the first batch of claims. Each handoff is documented in a shared tracker so nothing falls through the cracks.

Common role-assignment mistakes

Assigning the script installation to a marketer who only has CMS content access but not header access leads to a broken install. Letting the ad manager approve refunds without finance oversight can cause duplicate claims or missed credits. Assuming the agency will handle everything without a written agreement often results in no one owning the refund reconciliation step.

What to do if your team is missing a role

If you lack a dedicated developer, use Google Tag Manager or a similar tag manager that a marketer can edit. If there is no finance person, the founder or office manager can approve refunds as long as they have billing admin rights on the ad accounts. If the ad manager is external, require them to share read‑only access to the BotRefund dashboard so internal stakeholders can verify progress.

Decision criteria for assigning roles

Choose the right person based on who already has access and authority. The ad manager should be the one who can see the ad accounts and has a relationship with the platform reps. The developer must be someone who can edit the website code or tag manager. The finance person should be the one who handles billing and can approve spending disputes. If your team is small, one person may wear multiple hats, but the responsibilities should still be clear.

Step-by-step activation process

Step 1: The ad manager requests a free bot audit from BotRefund. This requires entering your ad spend range and contact details. No ad-account access is needed at this stage.

Step 2: A developer adds the BotRefund script to your website. The process takes about one minute. BotRefund provides a snippet that you paste into your site’s header or tag manager. The developer confirms the snippet fires in preview mode on all pages before publishing.

Step 3: The ad manager connects the ad accounts. This involves logging into Google Ads and Meta Ads and authorizing BotRefund to read click data and submit refund requests. The ad manager checks that GCLID and fbclid parameters are present in campaign URLs.

Step 4: Finance sets refund preferences. They decide whether refunds go back to the ad account as credits or are paid out, and they review the dispute logs. Finance reconciles approved refund credits in the ad account billing history to confirm the amounts match.

Step 5: The team reviews the first audit report. BotRefund identifies bot clicks and builds a case for refunds. The ad manager and finance together approve the submission.

Key facts about BotRefund activation

Limitations and when you might need more people

If your website uses a custom CMS or a complex tag management system, you may need a more experienced developer to ensure the script loads correctly. If your ad accounts are managed by an external agency, that agency's ad manager should be involved. Finance may need to coordinate with legal if the refund amounts are large or if there are contractual obligations with the ad platforms. In most cases, the three roles above are sufficient, but larger enterprises may add a dedicated fraud analyst or a compliance officer.

Frequently asked questions about team involvement

Can one person handle all the activation steps?

Yes, if that person has website access, ad-account access, and billing authority. But separating the roles reduces risk and ensures the refund process has proper oversight.

Does the developer need to be a web developer?

Anyone who can add a script tag to your website can do it. This could be a marketer with tag manager access, but typically a developer does it quickly and safely.

What if my ad accounts are managed by an agency?

The agency's ad manager should be the one to authorize the integration. You may need to provide them with the BotRefund script and instructions. Finance still handles refund preferences on your end.

Do I need to give BotRefund my ad account passwords?

No. The free audit does not require ad-account access. For refund claims, you authorize the connection through the platform's own account authorization flow without sharing your password with BotRefund.

How long does the activation take from start to finish?

Most teams complete the script installation and account connection within 30 minutes. The free audit runs immediately after the script is added, so you get results quickly.