Adobe Campaign Classic credentials
Configure the Adobe Campaign Classic credential fields offered by Platform Migration.
Current delivery: HTTP batch
- The credential form does not implement the provider’s complete native API or a choice of sync actions.
- Current delivery sends JSON row batches or a table-and-rows envelope. A compatible receiving endpoint must accept that format; a native provider API may require a separate adapter.
- Check the migration status and logs, then verify the records in the destination.
Configure the destination
- Open Platform → Migration and choose New Migration.
- Connect the source, select its tables, and choose Adobe Campaign Classic as the destination.
- Enter the credential fields below and use Test connection. Read the test scope before relying on its result.
- Confirm a compatible delivery endpoint is configured before attempting a transfer.
Credential fields
- Server URLRequired
- Adobe Campaign instance hostname, without https://.
- Client IDRequired
- OAuth client ID from Adobe Developer Console.
- Client secretRequired
- OAuth client secret from Adobe Developer Console.
- Organization ID
- Optional Adobe organization ID required for custom resources.
- API Key
- Optional key required for Campaign v8 and custom resources; it defaults to the client ID when omitted.
What the connection test checks
For this destination, Test connection checks the required configuration and any token setup performed by the connector. It does not make a destination data request. A successful result does not verify provider permissions or data delivery.
Use the credential inputs or a supported Secret Handler reference. Keep credentials out of source tables and shared examples. Inspect the run status and logs, then verify the destination content.
Need help with your setup? Visit the Help Center or contact Genorbex.