Source: https://bridgeeme.com/docs/parceiros.html

Documentation / Partners

# Partners

Integration

## What the partner receives

Click macroNative ID + Bridgee ID

Install matchneutral and versioned decision

Eligibilityconsent + contract + idempotence

Postbackdelivered, retry or suppressed 

Registration

## Rules per channel

| Channel | Entry | Exit | Note | 
| --- | --- | --- | --- |

| Google | gclid/gbraid/referrer | flow approved Google | deduplicate native assignment Firebase | 
| Meta | fbclid or approved payload | hired adapter | fbclid alone does not guarantee app postback | 
| TikTok | ttclid/payload approved | hired adapter | validate onboarding and Events Manager | 
| DSP | macro → partner_click_id | Configurable signed URL | schema, auth and window per partner | 

Postback

## Eligibility and delivery

```
one_resolved_paid_partner
 native_partner_evidence
 tenant_integration_enabled
 consent_and_region_allowed
 event_allowed_by_contract
 idempotency_key_not_delivered
= eligible_postback
```

Redirect and first-open are never network dependent. The decision creates an item in outbox; workers deliver with retry/backoff and auditable dead-letter.

Events

## What appears to the partner

| Event | Standard Bridgee | Minimum content | 
| --- | --- | --- |

| install | core | app, OS, timestamp, approved ID, consent, idempotence | 
| reinstall/reopen | by contract | only when partner policy allows | 
| purchase | not collected by SDK Bridgee | use Firebase/GA4 or customer's own integration | 
| quality summary | internal/opt-in | aggregate; do not replace conversion event | 

Audit

## How to track postbacks

### Status

queued, delivered, retry_wait, dead_letter or suppressed.

### Diagnosis

response status/code, attempt, next retry and reason codes; sensitive payload is redacted.

### Reconciliation

Compare idempotency key, window, event and daily total with partner dashboard.

Trust

## Why trust the results

- evidence-based decision, not channel priority;
- Opaque and preserved IDs without changing the case;
- conflicts suppress postback rather than choosing arbitrary winner;
- versioned contracts and shareable fixtures;
- outbox replay-safe and payload hash in audit;
- score separate from the attribution and always accompanied by coverage.

Partner onboarding

## Technical checklist

Register app, accounts and environments

Sandbox/testing before production.

Define macros and credentials

Secrets only in the server vault.

Map events and consent

No event is assumed due to name similarity.

Run fixtures

success, duplicate, expired, conflict, retry and revoked consent.

Activate by feature flag

Monitor divergence and maintain rollback per tenant.