Source: https://bridgeeme.com/blog/checklist-sdk-atribuicao/

Blog · Article

# Checklist before integrating an attribution SDK

Questions about scope, platform, examples, results, and maintenance to evaluate a app install attribution integration.

Bridgee · September 21, 2026 · 2 min

Contents
- [Scope and compatibility](https://bridgeeme.com/blog/checklist-sdk-atribuicao/#scope-and-compatibility)
- [Example and expected result](https://bridgeeme.com/blog/checklist-sdk-atribuicao/#example-and-expected-result)
- [Shared acceptance criteria](https://bridgeeme.com/blog/checklist-sdk-atribuicao/#shared-acceptance-criteria)

Before adding an SDK, define which question it should help answer and how your team will verify the result. This preparation reduces the chance of completing the technical installation without knowing whether the problem has been resolved.

## Scope and compatibility

- Which event will be identified and what source information is needed?
- Which operating system, application version, and channel are included in the test?
- Which version of SDK and which distribution were validated for the project?
- What happens when a signal is not available?

Don't use the success of one journey as confirmation of other platforms. Compatibility needs to match the environment that will be used.

## Example and expected result

Look for an example that the team can execute. Write the expected result before testing and include a journey where the source cannot be identified. Confirm that it is possible to distinguish legitimate absence of signal, configuration error and repeated processing.

Documentation should help locate the problem, record useful evidence, and request support without sending unnecessary credentials or data. The person responsible for maintenance needs to understand the procedure after the initial onboarding is complete.

## Shared acceptance criteria

The developer evaluates installation, execution and diagnosis. The person responsible for acquisition evaluates whether the result answers the business question. Both parties must agree on the definition of the event and the coverage limit.

In Bridgee, the [Get started](https://bridgeeme.com/start/) page presents the access path to the console. Creating the account and project does not automatically enable live installation integration. Activation and technical requirements must be confirmed during onboarding.

## Keep reading

- [MMP is dead. Long live GA4.](https://bridgeeme.com/papers/mmp-ga4-atribuicao/)
- [We only need Google Analytics.](https://bridgeeme.com/papers/google-analytics-origem-instalacoes/)
- [A download is not a first open.](https://bridgeeme.com/papers/download-instalacao-first-open/)

[Read or save as Markdown](https://bridgeeme.com/blog/checklist-sdk-atribuicao/index.md) · [Documentation](https://bridgeeme.com/docs/)

## Your next integration starts here.

Choose a product. Follow the guide. Connect your first project.

[Start building →](https://bridgeeme.com/start/)