FB Agency Ad Account Service for Affiliate Teams: A Pre-Launch Evidence Pack

Affiliate media buying often involves more parties than a direct-to-consumer campaign. The merchant may own the offer, an affiliate network may define the promotion terms, a media buyer may build the ads, a tracking platform may route clicks, and a separate team may control the landing page. When those responsibilities are scattered, an account provider cannot evaluate the campaign from a campaign name or destination URL alone.

When evaluating an FB agency ad account service, build one evidence pack for each offer and target market. The pack should show who is authorized to promote the offer, which claims can be supported, where every click goes, what data is collected, and who approves changes after launch.

This is not a shortcut around Meta's review systems. Meta says ad review may examine images, video, text, targeting information, and the destination, and an active ad may be reviewed again. Meta does not publish a universal evidence-pack requirement for affiliate teams; the pack described here is an internal and provider readiness record, not a Meta application form. Its purpose is to make a legitimate campaign easier to assess and operate consistently.

The Short Answer

For its own readiness review or a provider's onboarding process, an affiliate team should maintain an Offer × GEO evidence pack with a unique version for each combination of:

• Offer or merchant
• Target country or region
• Funnel and destination path
• Creative and claim set
• Tracking configuration
• Commercial limits
• Approval status

The same offer may have different permissions, required disclosures, audience restrictions, payout terms, or landing pages in different markets. Treating every market as one campaign package can hide important differences.

A useful pack allows a provider or internal reviewer to answer five questions quickly:

1. Who is responsible for the advertising?
2. Is the team authorized to promote this exact offer in this exact market?
3. Does the ad accurately match the complete customer journey?
4. Can each material claim be traced to evidence?
5. Will the team know when a change requires an internal or provider review, a campaign update, or a pause?

Why Affiliate Campaigns Need an Offer-Level Record

In a direct brand setup, the advertiser may control the product, website, creative, customer data, and advertising account. In affiliate marketing, those controls may be distributed across several organizations.

For example, a media buyer may receive an approved offer from a network but have no authority to edit the merchant's checkout. A creative team may work from an old promotion sheet. A tracker may send visitors through different paths by device or country. The merchant may change pricing or terms without notifying the buyer.

These are operational risks even when every party intends to follow the rules. A static application form may not capture all of them. An offer-level record creates a shared source of truth for the team that buys media, the provider that reviews the request, and the people responsible for the destination.

It also separates three decisions that are often confused:

• Commercial acceptance: the network or merchant allows the affiliate to promote the offer.
• Provider acceptance: the provider is willing to support the business and proposed setup.
• Platform decisions: Meta reviews ads against its Advertising Standards and separately may require advertiser verification or restrict ad accounts and other business assets under its own enforcement processes.

Approval at one layer does not automatically establish approval at the other layers.

1. Map the Responsibility Chain

Start the pack with a one-page responsibility map. Name the actual organizations and people; do not use labels such as “client,” “partner,” or “owner” without identifying who they are.

If one company performs several roles, state that clearly. If a role is shared, identify the final decision maker.

The responsibility map should also explain who can pause campaigns immediately. A media buyer should not need to locate an unknown merchant contact after a page, price, or claim changes.

2. Assemble the Offer Authorization Record

An offer name or screenshot from a network dashboard is not a complete authorization record. Store the information required to connect the affiliate, offer, market, and promotion method.

Include, where applicable:

• Merchant or brand name
• Affiliate network name
• Affiliate account or publisher ID
• Offer ID and current offer name
• Authorized countries or regions
• Permitted traffic sources
• Prohibited promotion methods
• Brand-name, logo, image, or creative permissions
• Promotion start and end dates
• Price, discount, trial, renewal, and cancellation terms
• Required disclosures or disclaimers
• Category-specific authorization, registration, or licensing evidence
• Network or merchant contact who confirmed the terms
• Date the authorization was checked

Store the original document or message, not only a team member's summary. If authorization exists only inside a dashboard, retain the stable record available to the business and record when it was captured. Do not alter a document to make an unsupported market or traffic source appear eligible.

Intellectual-property permission also matters. Meta's Advertising Standards prohibit third-party intellectual-property infringement, including copyright and trademark infringement. An affiliate agreement may permit traffic generation without permitting unrestricted use of a brand's logo, customer testimonial, or copyrighted creative. Confirm the scope separately.

3. Build an Offer × GEO Eligibility Matrix

Create one row for every market the campaign may target. Do not copy “worldwide” from a sales message unless the offer owner and the relevant business requirements support that conclusion.

The matrix is an operational control, not a legal opinion. Requirements may depend on the product, jurisdiction, customer, targeting, and current platform rules. Assess the applicable requirements as separate, potentially overlapping layers: whether the campaign must be declared as a Special Ad Category; whether the offer, creative, or destination falls under a restricted or prohibited-content rule in Meta's Advertising Standards; and whether Meta imposes category-specific permission, authorization, verification, age, or targeting requirements. Separately confirm the applicable local legal requirements for each market.

Use separate rows when two countries share a language but not the same product terms. Also separate mobile and desktop funnels when they lead to materially different pages or purchase flows.

4. Capture the Complete Funnel, Including Redirects

Meta states that ad review can include the destination associated with an ad. For affiliate teams, the visible landing-page URL may be only one part of the journey.

For internal and provider assessment, record the customer-facing path that can follow the ad click:

1. Ad creative and copy
2. Displayed link and call to action
3. Tracking link
4. Every redirect
5. Pre-lander or bridge page
6. Merchant landing page
7. Lead form or checkout
8. Upsell or confirmation page
9. Customer terms, privacy notice, refund information, and support route

For each step, record the URL, domain owner, page owner, purpose, active market, and last review date. Capture both mobile and desktop paths. Test without an internal login and from the target market when lawful and practical, because routing can differ by location, device, browser, or parameter.

Meta's advertising policy checklist says a linked website should work, be clearly accessible, relate to the ad, and avoid misleading or disruptive experiences. Test for broken pages, unexpected redirects, certificate warnings, forced downloads, misleading buttons, missing product information, and material differences between the ad and final offer.

Meta's Advertising Standards prohibit deceptive links, and Meta's Community Standards describe cloaking as deliberately showing its integrity systems different off-platform content from what users receive in order to evade enforcement. Do not use routing logic to show Meta's integrity systems a materially different offer or destination from the one customers receive. A legitimate tracker should support measurement and authorized routing, not conceal the real destination. Normal redirects or localization are not automatically cloaking; the relevant risk is using different content to evade review or enforcement.

5. Maintain a Creative Claims Ledger

Do not approve a creative merely because it came from a network, merchant, or swipe file. Break it into individual claims and verify each one.

Review implications as well as literal words. An image, before-and-after sequence, countdown, badge, or page layout can communicate a message even when the copy does not state it directly.

Meta's Advertising Standards prohibit identified deceptive or misleading practices. The claims ledger proposed here is an internal substantiation control, not a universal Meta evidence-submission requirement. Use it to check that prices, results, scarcity statements, testimonials, comparisons, and endorsements are current, supported, properly qualified, and consistent with the customer-facing destination. Evidence alone does not make content eligible if another Meta policy prohibits it.

The ledger should identify:

• The exact approved wording
• Any required qualifier or disclosure
• The evidence source and date
• The page section where the customer can verify the claim
• Who has authority to approve changes
• The creative files that use the claim
• The markets and languages in which it is approved

If the merchant changes the evidence or withdraws permission, the team must be able to locate every affected ad quickly.

6. Diagram the Tracking and Data Flow

Affiliate measurement may connect several systems. The evidence pack should show how data moves, not just list tool names.

Map:

• Meta dataset ID and each connected data source, such as the Meta Pixel or Conversions API
• Affiliate tracking platform
• Network postback
• Merchant or lead-buyer system
• CRM or analytics platform
• Consent and privacy controls
• Event names and optimization event
• Data owner and integration owner
• Access needed to troubleshoot the flow

For each event, record the customer action it represents, which system sends it, the event name, identifiers and parameters used, and who can change the configuration. Meta describes events as actions people take in customer-facing experiences. Review custom events in Events Manager, and block any event you cannot confirm originates from your business and complies with the Meta Business Tools Terms.

Identify where personal information is collected and which Meta Business Tools receive Event Data. Meta's Business Tools Terms require clear and prominent notice on relevant webpages and any consent required by applicable law. Meta also prohibits specified categories of information, including certain health and financial information, from being sent through its Business Tools, including when that information appears in URL parameters. Review Meta's privacy and data-use requirements and prohibited-information guidance for the actual implementation.

The account provider does not need unrestricted access to every system. Share the information needed to understand the proposed setup, and grant operational access only where the documented role requires it. For a detailed access-control process, see the Facebook agency account access guide.

7. Add Affiliate-Specific Commercial Guardrails

An offer can be policy-ready but economically unsuitable. Record the commercial limits at the offer level so the buyer does not scale based on an outdated payout or an unverified conversion rate.

Include:

• Current payout and qualifying conversion definition
• Hold, reversal, validation, and payment terms
• Daily or monthly traffic cap
• Approved target markets
• Test budget
• Maximum acceptable acquisition cost
• Stop-loss rule
• Minimum data requirement before a scale decision
• Owner who can authorize budget increases
• Date the commercial terms were last confirmed

These controls are internal business rules. They do not change Meta's billing, review, or enforcement decisions. They also should not be confused with provider funding terms, which must be documented separately.

Avoid building a test plan around projected results presented as certainty. Treat payout, conversion quality, approval rate, and acquisition cost as variables to be measured under the actual campaign conditions.

8. Version the Pack and Control Changes

The evidence pack loses value if the pages and ads can change without a trace. Assign each pack a stable identifier, such as:

OFFER-204_US_EN_v1.3_2026-09-02

The identifier should show the offer, market, language, version, and effective date. Maintain a change log with:

• Date and time
• Previous and new version
• Component changed
• Reason for change
• Person who requested it
• Evidence reviewed
• Person who approved it
• Campaigns affected
• Required action: no action, internal review, provider notice, ad edit, pause, or new submission

Changes that should trigger a documented review include:

• A new merchant, offer owner, or network
• A different offer URL or redirect path
• A new pre-lander or page template
• A material price, trial, billing, refund, or fulfillment change
• A new claim, testimonial, visual implication, or promotion deadline
• A new country, audience, or language
• A change to the product category or customer eligibility
• A different tracker, event, postback, or data recipient
• A material change to required disclosures
• Expired or withdrawn authorization

Do not assume that keeping the same URL preserves the prior risk assessment or prevents Meta from reviewing the destination again. The content and customer journey matter, not only the domain.

Meta states that creating or editing an ad starts the review process, and some edits can initiate another review. Build the workflow around the current campaign state rather than treating an earlier approval as permanent.

9. Use a Two-Stage Launch Gate

Before any campaign goes live, require both an evidence decision and an execution decision.

Stage A: Evidence Ready

• Responsibility chain is complete.
• Offer authorization is current.
• Offer × GEO matrix allows the proposed traffic.
• Complete funnel has been tested and recorded.
• Claims ledger is approved.
• Tracking and data map is current.
• Required disclosures are present.
• Commercial guardrails are signed off.
• Pack version is frozen for internal or provider approval and the final campaign build.

Stage B: Build Matches the Pack

• Final ad copy matches the approved claim wording.
• Final creative is the reviewed file version.
• Targeting uses the approved market and audience.
• Destination and redirect chain match the funnel record.
• Tracking uses the documented events and parameters.
• Campaign owner and pause contact are available.
• Launch budget remains within the approved test limit.

The buyer who built the campaign should not be the only person checking it. A second reviewer can catch stale URLs, copied targeting, mismatched currencies, missing disclosures, and unapproved creative changes.

10. Use the Pack to Identify Post-Launch Drift

The approved pack becomes a baseline after launch. Compare the live campaign and customer journey with that exact version whenever delivery changes, an ad is rejected, customer complaints appear, or a merchant announces an update.

Check for drift in this order:

1. Merchant drift: price, product, terms, checkout, fulfillment, or authorization changed.
2. Funnel drift: a page, redirect, domain, localization rule, or device path changed.
3. Creative drift: the live copy or file no longer matches the claims ledger.
4. Market drift: targeting, audience, language, or destination differs from the approved Offer × GEO row.
5. Tracking drift: an event, postback, parameter, data recipient, or optimization action changed.

Record the first mismatched component, the time it changed, affected campaigns, and the person responsible for correcting it. This turns the pack into a diagnostic record instead of a folder that is forgotten after launch.

For the general Meta rejection and account-continuity process, use the separate Facebook ad account disabled recovery guide. Meta also publishes its own rejected-ad troubleshooting steps, including editing or recreating an ad and requesting another review where that option is available.

11. Package the Files for Provider Review

Use a predictable folder and index so the reviewer can locate evidence without searching through chat history.

00-Pack-Index
01-Responsibility-Map
02-Offer-Authorization
03-Offer-GEO-Matrix
04-Funnel-and-Redirect-Record
05-Creative-Claims-Ledger
06-Creative-Files
07-Tracking-and-Data-Map
08-Commercial-Guardrails
09-Approvals
10-Change-Log

The index should state:

• Pack ID and version
• Advertiser and affiliate entity
• Merchant, network, offer ID, and target GEO
• Destination domains
• Proposed launch date
• Expected monthly spend and required account quantity
• Named campaign owner
• Open questions or unresolved conditions
• Reviewer, decision, and date

Mark missing information as missing. An honest unresolved item is easier to manage than an assumed answer embedded in an incomplete pack.

Record the Provider Review Decision

Do not reduce the provider's response to “approved” in a chat thread. Add a decision record to the pack that identifies:

• Pack ID and exact version reviewed
• Offer, GEO, language, funnel, and account configuration covered
• Decision date and reviewer
• Conditions that remain unresolved
• Items that must change before launch
• Evidence that expires and its renewal date
• Changes that require a new submission
• Campaigns linked to the decision

If the provider's decision covers only one market or funnel version, do not apply it to another. If a condition is unclear, record the question and obtain a written answer before launch. Business-level ownership, access, funding, and support terms should remain in the separate provider agreement; the evidence pack records the decision for this offer. Use the Facebook agency ad account provider checklist for that separate commercial review.

Discuss an Affiliate Account Setup With AdAccRun

To request an account assessment, contact AdAccRun on Telegram with the advertising platform, business and offer, target GEO, expected monthly spend, required account quantity, and the current Offer × GEO evidence pack.

Availability and setup remain subject to AdAccRun's business and landing-page review. Account access does not replace Meta's Advertising Standards, ad review, any verification or authorization Meta requires for the advertiser, category, or market, or Meta's enforcement decisions.

Frequently Asked Questions

Does an affiliate network approval mean Meta will approve the ads?

No. Network or merchant authorization may establish commercial permission and permitted promotion methods, but it is not Meta approval. Meta separately reviews the ad and its destination against its Advertising Standards, and may also require advertiser verification or restrict advertising assets.

Should one evidence pack cover all GEOs?

Only when every material condition is genuinely the same. Separate the records when authorization, price, disclosures, language, audience, destination, fulfillment, or legal requirements differ. An Offer × GEO structure makes those differences visible.

Do we need to disclose every redirect to the provider?

For this evidence-pack assessment, record every redirect that can change the destination, content, or customer experience, and document tracking-only redirects separately. This is an internal or provider review control, not a universal Meta document-submission requirement. Deceptive destination behavior may still violate Meta's rules on deceptive links.

What if the merchant changes the landing page after launch?

Compare the new page with the approved pack immediately. If the change affects the offer, claims, price, terms, disclosures, routing, data collection, or customer experience, pause or limit affected campaigns until the team completes its internal or provider review and updates the pack.

Is the evidence pack a one-time application document?

No. It is an operating record. Update it when the offer, market, funnel, creative, claim, tracking, authorization, or commercial terms change, and link every live campaign to its current version.

Does a network dashboard screenshot prove offer authorization?

Not by itself. A screenshot may help identify the network account, affiliate ID, or offer, but it may omit the permitted GEOs, traffic sources, dates, claim limits, creative rights, and current terms. Retain the underlying agreement or current network record and identify a contact who can confirm the authorization.