Email Campaigns

LastDatabase Email Campaigns provides a structured workspace for building audiences, preparing campaign content, reviewing recipient eligibility, and submitting campaigns for mandatory staff compliance and abuse review.

What is LastDatabase Email Campaigns?

Email Campaigns is the campaign-management layer of the LastDatabase platform. It is designed to organize the work that happens between selecting an audience and delivering an email campaign.

Instead of exposing a direct bulk-send button, the workflow separates audience preparation, email verification, campaign content, recipient eligibility, staff review, and eventual delivery.

The delivery stage completes the campaign lifecycle by applying final recipient eligibility checks before approved messages enter the controlled delivery pipeline.

Quick start

1. Open Email Campaigns.
   Sign in and open Email Campaigns from your customer dashboard.
2. Create an audience.
   An audience groups the contacts you intend to use for a campaign.
3. Import eligible contacts.
   The current audience workspace supports external CSV contact imports. Only import contacts you are permitted to use.
4. Review verification and suppression information.
   Use the available data-quality and eligibility controls before preparing the campaign.
5. Create a campaign.
   Choose your audience and configure the sender identity, subject, preview text, HTML content, and plain-text content.
6. Preview and edit.
   Review the campaign before submitting it.
7. Submit for staff review.
   A campaign must enter the mandatory compliance and abuse review workflow before it can advance toward delivery.

1. Create an audience

An audience is a collection of contacts associated with your account. Campaigns reference an audience rather than accepting an uncontrolled list of addresses directly at the sending stage.

Open the audience workspace from Email Campaigns and choose Create Audience. Give the audience a descriptive name that explains its purpose or source.

Examples might include a customer newsletter list, event registrants, product subscribers, or another audience that your organization is permitted to contact.

2. Import external CSV contacts

The current audience workflow supports external CSV contact imports. The import process associates contacts with your selected audience.

External contacts are treated separately from LastDatabase lead records. For externally supplied contacts, the platform can retain information about the source and permission status associated with the import.

Contact information

Campaign contact records can support information such as:

• Email address
• First name
• Last name
• Company
• Source
• Source record identifier
• Verification status
• External permission status where applicable
• Suppression status

3. Email verification

Email verification is a separate data-quality function. You can use the Email Verifier to evaluate technical signals associated with an email address.

Verification can evaluate signals including syntax, domain configuration, DNS, MX records, and SMTP-related information where available.

See the complete Email Verifier documentation for result interpretation and verification limitations.

4. Suppression and recipient eligibility

Suppression controls are an essential part of the campaign architecture. A recipient may become ineligible because of an unsubscribe, complaint, hard bounce, manual suppression, or another applicable restriction.

Suppression is separate from the original contact source. This means suppression requirements apply even when a record originally came from LastDatabase.

5. Create a campaign

After preparing an audience, open Email Campaigns and choose the campaign creation option.

A campaign combines an audience with sender information and the message content that will be reviewed.

Select an audience

Choose the audience associated with the campaign. The audience establishes which group of contacts the campaign is intended to evaluate for use.

Configure sender information

Provide the sender information requested by the campaign form. This can include:

• From name
• From email address
• Reply-To address

Sender-domain authentication protects sender identity and supports deliverability. The campaign delivery architecture uses domain verification together with standards such as SPF, DKIM, and DMARC before an authenticated sender is used for campaign delivery.

Write the subject

Enter a clear subject that accurately represents the content of the message. Avoid deceptive subject lines or sender identities.

Add preview text

Preview text can provide additional context next to or below the subject in email clients that support it.

Create HTML content

The HTML version contains the formatted campaign content. Review links, layout, wording, identity information, and the intended recipient experience before submission.

Create plain-text content

Where applicable, provide a useful plain-text representation of the campaign rather than relying only on HTML.

6. Save and edit drafts

A campaign begins as a draft. Draft status allows you to prepare and revise campaign information before submitting it for staff review.

Review the audience, sender identity, subject, preview text, HTML content, and plain-text content carefully before submission.

7. Preview the campaign

The campaign detail workspace provides a campaign preview so you can inspect the content before submitting it.

A preview is useful for content review, but it does not reproduce every email client's rendering behavior. Production rendering can vary between mailbox providers, devices, and applications.

8. Submit for staff review

When the campaign is ready, submit it for mandatory staff compliance and abuse review.

Submitting does not send the campaign. It changes the campaign from the customer drafting workflow into the review workflow.

9. What staff review examines

The review workflow is designed to provide an additional control between campaign creation and bulk delivery.

Review information can include:

• Customer and campaign information
• Audience source
• Audience size
• Sender identity
• Subject line
• Reply-To information
• Campaign content
• Rendered preview
• Available automated checks
• Recipient eligibility and suppression considerations

10. Review decisions

A reviewer can approve a campaign, request changes, or reject it.

Changes requested

If changes are requested, review the reason supplied by staff, update the campaign, and submit the revised version again when ready.

Rejected

A rejected campaign does not advance toward delivery. Review the reason associated with the decision before preparing another campaign.

Approved

Approval means the reviewed campaign version passed the platform's staff review stage. The approved version can then advance to final eligibility, suppression, sender-authentication, allowance, and delivery controls.

11. Approval content integrity

LastDatabase associates campaign approval with the reviewed campaign content. Material campaign changes after review can invalidate the approval and require another review.

This prevents one version from being approved and then materially changed into a different campaign without review.

12. Campaign statuses

13. Final pre-send controls

The complete delivery architecture is designed to perform another eligibility check after approval and before messages enter the sending queue.

The intended final checks include:

• Staff approval remains valid
• Approved campaign content has not materially changed
• Sender identity and domain remain eligible
• The customer account remains active
• The applicable sending allowance is available
• The recipient remains eligible
• Unsubscribe status is checked
• Hard-bounce suppression is checked
• Complaint suppression is checked
• Manual suppression is checked
• The applicable verification policy is satisfied

Only recipients that remain eligible after these final controls should advance into the campaign delivery queue.

14. Sender domains and authentication

Production email delivery requires sender authentication and reputation controls. The delivery architecture is designed to support sender-domain verification and common authentication standards such as SPF, DKIM, and DMARC.

Authenticated sender domains are used to establish approved sending identity before campaign messages enter the delivery pipeline.

15. Delivery architecture

The planned production delivery path separates campaign management from mail transport.

The intended flow is:

Customer workspace → Audience eligibility → Suppression checks → Campaign approval → Final checks → Queue → Delivery provider → Recipient → Delivery events → Analytics

This design allows the application to manage campaign state and policy while a dedicated email-delivery layer handles mail transport.

16. Bounce handling

The delivery architecture is designed to process bounce events and suppress addresses when a hard-bounce condition makes continued delivery inappropriate.

Hard-bounce events feed the suppression system so addresses that should not receive additional messages can be excluded from subsequent campaign processing.

17. Complaint handling

Complaint signals are intended to feed the suppression system so affected addresses do not continue through ordinary campaign delivery.

Delivery-provider webhook events can update campaign activity and suppression state when complaint information is received.

18. Unsubscribe handling

The campaign architecture requires unsubscribe and suppression controls. An unsubscribe must affect recipient eligibility regardless of whether the original record came from an external import or LastDatabase.

Unsubscribe state is checked as part of recipient eligibility and must be applied before an address can advance into campaign delivery.

19. Campaign analytics

The planned analytics layer is designed to use delivery-provider events to report campaign performance and operational signals.

Relevant metrics can include:

• Accepted or processed recipients
• Delivered messages
• Bounces
• Complaints
• Clicks
• Unsubscribes

Open tracking can be affected by mailbox privacy features and automated image loading, so open counts should not be treated as a perfect measure of human engagement.

Campaign analytics combine delivery and recipient-event information so customers can evaluate campaign performance and operational quality.

20. LastDatabase lead integration

The campaign architecture is designed to support two distinct audience sources:

• Customer-owned or externally imported contacts
• Eligible LastDatabase lead records

LastDatabase lead integration connects eligible lead access with the campaign audience system. Lead entitlement remains separate from campaign sending allowance and verification credits.

When enabled, LastDatabase lead access will still remain subject to recipient eligibility, suppression, unsubscribe, campaign review, and other applicable controls.

21. Lead credits, verification credits, and sending allowance

Lead access controls access to applicable LastDatabase lead records.

Verification credits apply to supported Email Verifier usage.

Email sending allowance applies to the number of campaign emails included in the applicable Email Campaigns plan.

Purchasing or receiving one type of allowance does not automatically provide the other two.

22. Email Campaigns pricing

The Email Campaigns plans are structured around monthly email sending allowances.

Plan limits refer to email sending allowance. They do not represent lead credits or Email Verifier credits.

See the public Email Campaigns page for current product information.

23. Complete Email Campaigns system

The Email Campaigns system is organized as a connected set of campaign management, eligibility, review, delivery, and reporting components.

24. Recommended campaign workflow

1. Create a clearly named audience.
2. Import only contacts you are permitted to use.
3. Remove duplicates and review recipient eligibility.
4. Use email verification when appropriate.
5. Respect existing suppression and unsubscribe information.
6. Create accurate sender information.
7. Write a clear and non-deceptive subject.
8. Prepare useful HTML and plain-text content.
9. Preview the complete campaign.
10. Submit the campaign for staff review.
11. Respond to requested changes when applicable.
12. Do not assume approval guarantees legality or inbox placement.

25. Frequently asked questions

How does a campaign advance to delivery?

A campaign is prepared in the customer workspace and submitted for mandatory staff compliance and abuse review. After approval, the campaign advances through final recipient eligibility, suppression, sender, allowance, and delivery controls before eligible messages enter the delivery pipeline.

Can I import my own contacts?

Yes. The current audience workspace supports external CSV contact import. You remain responsible for the source and permitted use of imported contacts.

How do LastDatabase leads work with Email Campaigns?

Eligible LastDatabase lead records can be connected to campaign audiences according to the customer's applicable lead entitlement. Lead access, verification credits, and campaign sending allowance remain separate. Suppression and recipient eligibility controls still apply.

Does every campaign require review?

Yes. Campaigns must pass the mandatory staff compliance and abuse review workflow before advancing toward delivery.

Does staff approval guarantee that a campaign is legally compliant?

No. Staff review is a platform abuse and compliance control. It cannot guarantee compliance with every law, jurisdiction, recipient relationship, or customer-specific circumstance.

Does a verified email guarantee delivery?

No. Verification is a point-in-time technical assessment. Delivery can still be affected by mailbox configuration, sender reputation, content, provider policy, rate limits, filtering, and other factors.

Are Email Campaigns sends the same as verification credits?

No. Email sending allowance and Email Verifier credits are separate. Lead access is also a separate service.

What happens if I edit an approved campaign?

Material changes can invalidate the approval associated with the reviewed campaign version and require another review.

How are unsubscribed recipients handled?

The platform architecture treats unsubscribe status as a recipient eligibility restriction regardless of the original contact source. Production unsubscribe enforcement is part of the delivery-stage system.

Where can I learn about Email Verifier?

See the Email Verifier documentation for verification signals, results, limitations, and credit information.