NextRoll

NextRoll is an online platform that provides digital marketing services that companies can use to grow their business. Its machine learning technology gathers data, delivers insights, and provides businesses with approachable tools to target buyers in strategic ways.

In order to integrate NextRoll with Relyance AI you will need a Client ID, Client Secret, and follow an OAuth2 flow.

In NextRoll:

1. Login to your NextRoll account.
2. Go to the Developer portal here: https://developers.nextroll.com/
3. Click on the user profile menu in the top right-hand corner and select Apps.
4. Click the + NEW APP button.
5. Fill out the New App form with the following: App Name: A meaningful name (e.g. Relyance AI). Description: A meaningful description. Starter API Access: Click the Enable button. Callback URL: https://root.relyance.ai/api/oauth2
6. Click SAVE to create your app.
7. Copy the Client Key and Client Secret to be used in Relyance.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the NextRoll integration card and click it to open its connections.
6. Under Authentication Method, choose Oauth2 / App Token.
7. Paste the Client ID and Client Secret into their respective fields.

9. Click Authenticate.
10. This will bring you to the AdRoll site to sign in and authorize Relyance.

You will need an account for both NextRoll and AdRoll. 11. At this point, you should see the following result on the Vendor Integrations page:

12. Congratulations, you are now connected to NextRoll.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example nextroll/<connection_id>) or reading it with the relyance_integration_connection data source.