- Campaign v7 documentation
- Latest updates
- Release Notes
- Get started
- Start with Adobe Campaign
- Privacy
- Profile management
- Import and export data
- Filter data
- Create queries
- Permissions
- Data packages and enumerations
- Connectors
- Create and send messages
- Get started with messages
- Key steps when creating a delivery
- Send emails
- Send SMS
- Send LINE messages
- Send push notifications
- Send direct mail
- Use delivery templates
- Personalize deliveries
- Use seed addresses
- A/B testing
- Services and subscriptions
- Monitor deliveries
- Track messages
- Deliverability management
- Content management module
- Orchestrate marketing campaigns
- Marketing Resource Management
- Distributed marketing
- Response manager
- Design and share reports
- Design web content
- Create online surveys
- Integrate with Adobe Experience Cloud
- Automate with workflows
- Get started with workflows
- Execute a workflow
- Targeting activities
- Flow control activities
- Action activities
- About action activities
- Delivery
- Delivery control
- Continuous delivery
- Recurring delivery
- Cross-channel deliveries
- Local approval
- Data loading (RDBMS)
- Loading (SOAP)
- Data loading (file)
- Content Management
- Data extraction (file)
- SQL code and JavaScript code
- SQL Data Management
- Nlserver module
- Update aggregate
- Event activities
- Use cases
- Monitor workflows
- Advanced management
- Manage Offers
- Transactional Messaging
- Integrate with social media
- Installation and configuration guide
- Architecture principles
- Deployment types
- Security and privacy settings
- Install Campaign (on-premise)
- Deploy Campaign (on-premise)
- Configure Campaign
- Connect to Campaign
- Connect Campaign to external systems
- Configure external accounts
- Configure Federated Data Access
- Get started with Federated Data Access
- Best practices and limitations
- Configuration guidelines
- Configuration steps
- Configure Amazon Redshift
- Configure Azure Synapse
- Configure Google BigQuery
- Configure Hadoop
- Configure Microsoft SQL Server
- Configure Netezza
- Configure Oracle
- Configure PostgreSQL
- Configure SAP HANA
- Configure Snowflake
- Configure Sybase IQ
- Configure Teradata
- Configure Vertica Analytics
- Remote access rights
- Connect to the database
- Create the data schema
- Define data mapping
- Appendices
- Monitoring guide
- Developers guide
- Technotes
- Campaign Control Panel
About seed addresses
Seed addresses are used to target recipients who do not match the defined target criteria. This way, recipients who are out of the delivery scope can receive the delivery, as any other target recipient would.
Once of the main reason for using them is your mailing list protection. Inserting seed addresses into your mailing list lets you be noticed if it is being used by a third party, as the seed addresses it contains will receive the deliveries sent to your mailing list.
Moreover, seed addresses let you preview and test the deliveries personalization and rendering before their sending, by sending them proofs (see Use seed addresses as proof).
Discover this feature in video
The seed addresses feature has the following benefits:
- Random substitution of fields with data taken from recipient profiles: this lets you enter only the email address, for instance in the seed address section, and let Campaign automatically fill in the other fields form the profile (see Use case: configure the field substitution).
- When using a workflow with Datamanagement functionalities, the additional data processed in deliveries can be entered at seed address level to force values: this sidesteps random value substitution.
- Seed addresses are automatically excluded from reports on the following delivery statistics: Clicks, Opens, Unsubscriptions.
Seed addresses are added to the target of deliveries by being imported or by being created directly in the delivery or the campaign.
Seed addresses do not belong to the recipients table, they are created in a separate table. If you extend the recipients table with new data, you have to extend the seed addresses table as well with the same data. Otherwise, they extended fields will not be taken into account for seed addresses.
An example of how to extend the seed addresses table is presented in this section: Use case: select seed addresses on criteria.
For direct mail deliveries, seed addresses are added during extraction and mixed in the output document.
For direct mail deliveries, the extraction file format must comply with the following limitations:
- It must not use the option Handle groupings (GROUP BY+HAVING).
- If element collections are extracted, these fields will have an empty value for the seed addresses, unless the Single row (expert user) option is selected. For more on this, refer to this section.
Resources
Adobe Account
