An AWS Partner Central lead is an early-stage prospect in APN Customer Engagements (ACE), before qualification into an opportunity. ACE-eligible partners can create leads from their own account lists and then enrich them with AWS signals. Creating and enriching are separate operations.
For a Salesforce target-account list, the work is to select companies, supply a primary contact, map the data to AWS’s format, create the leads and inspect enrichment results. You can use a CSV import for a one-off list or the Selling API for an integration. A connector’s schedule and validation rules are separate from AWS’s rules.
What is the difference between creating and enriching a lead?
Creating adds a partner-originated lead to ACE. Enriching requests AWS’s readiness assessment and insights for an existing lead. A rejected create leaves no lead; a completed enrichment can leave a valid lead with no insights.
| Step | Console route | API route | Result to retain |
|---|---|---|---|
| Create | Import leads, using a CSV of 1 to 100 rows | Programmatic lead creation | The created lead and its source-account association, or the failure reason |
| Enrich | Select leads on Leads, choose Enrich leads, name the batch | An asynchronous prospecting task of up to 100 leads, processed independently | Each lead’s result, including leads for which data was unavailable |
AWS announced lead enrichment on June 15, 2026. The announcement names both console uploads and programmatic creation, and availability to ACE-eligible partners.
This article covers outbound account lists. For the inbound path, see Marketplace buyer requests lacking enough business context and the invitation question below.
What should you prepare from Salesforce?
Prepare the company record and a real primary contact before submitting anything. A Salesforce Account supplies company fields; selecting that Account alone does not decide which person should represent the lead.
The table gives AWS’s input formats and corresponding Account fields to inspect. Treat the Salesforce column as a preparation aid, not a promise that every connector maps it that way.
| AWS input | Salesforce data to inspect | AWS format |
|---|---|---|
| Company name | Name | Up to 120 characters |
| Website | Website | URL format, 4 to 255 characters |
| Industry | Industry | An accepted AWS industry value |
| Country | BillingCountry | ISO 3166-1 alpha-2 code |
| State or region | BillingState | Free text |
| City, postal code | BillingCity, BillingPostalCode | Up to 255 and 20 characters respectively |
| Phone | Check the contact and the connector’s mapping | E.164 preferred |
| Use case, business problem | Fields your team chooses | Up to 255 and 2,000 characters |
| Contact first name, last name, email, business title | The selected contact | Up to 80 characters each; valid email format |
AWS’s import instructions require the template’s column headers and validate required fields, formats and accepted values. Common failures include missing company names or emails, invalid country codes and industries that do not match AWS’s values.
For the contact, choose a rule your team can explain and review. A domain match can be useful, but it is not a substitute for knowing which person owns the relationship. Record how a contact was selected so that an account owner can correct the source when a submission fails.
Normalize data before export. A country name in Salesforce and a two-letter AWS code are different representations; an industry label valid in your CRM need not be valid in AWS. Check the translated result rather than assuming a populated field will pass.
How do you import, enrich and check a first batch?
Use a small, reviewable account list first, then inspect creation and enrichment independently. The following is an operating sequence based on AWS’s separate import and enrichment actions.
- Select the Accounts. Define which prospects belong in the batch and retain their Salesforce record IDs in your working list. This makes it possible to reconcile a failure with the original company.
- Choose and check contacts. Confirm the company and contact data against the AWS template. Do not fabricate missing people to make the file pass validation.
- Import the CSV. Keep within 1 to 100 rows and inspect the per-row results. AWS provides a failed-records file to support correction. Re-uploading the same CSV on the same day does not create duplicate leads; do not assume that statement describes every cross-day or API retry.
- Enrich the created leads. On the Leads tab, select them, choose Enrich leads and name the batch. Review it under Enriched lead batches.
- Reconcile both steps. Separate rows never created from existing leads with no enrichment data. Fixing the former requires correcting a submission; the latter may have nothing to fix.
- Assign follow-up. Use readiness to prioritize outreach, then update qualification as the team investigates the prospect.
For an API integration, preserve the same separation in its records. An accepted request is not evidence that every member of an asynchronous enrichment task returned useful data. Inspect each lead’s result before recording the batch as complete.
What does AWS enrichment return?
AWS returns a readiness recommendation with a High, Medium or Low confidence level, plus marketplace and company insights. AWS’s enrichment guide defines the recommendations:
| Readiness | Follow-up AWS suggests |
|---|---|
| Contact Ready | Prioritize immediate outreach |
| Nurture Lead | Follow up through marketing nurture |
| Limited Potential | Deprioritize because of low propensity |
The four insights answer different questions:
- AWS Marketplace engagement score estimates likelihood to procure through the marketplace, scored High, Medium or Low.
- AWS Marketplace solution score estimates likelihood to buy a category-specific solution.
- Account eligibility checks select program, funding-benefit and sales-motion eligibility. The announcement names the Partner Greenfield Program, Pioneer Credits and the Partner-Led Sales Motion.
- Firmographics includes employee count, region and geography.
Read eligibility as a check, not funding already awarded. A readiness signal also does not replace sales qualification: the team still has to establish that the opportunity is real.
AWS’s Partner Lead Prospecting, announced July 9, 2026, builds on enrichment. Its sales plays, call scripts and outreach emails unlock after the lead has been enriched. Those assets support the next conversation; they do not change the distinction between creating the record and enriching it.
When can a lead become a co-sell opportunity?
A lead can be converted once it reaches Qualified. AWS’s lead-management guide treats updating and conversion as further lifecycle actions, separate from import and enrichment.
Keep the original CRM association available through qualification so the opportunity owner can trace the prospect back to the source account. The wider opportunity lifecycle is covered in how AWS ACE co-selling works for ISVs.
How Fours handles Salesforce Accounts
Fours offers a scheduled Account sync and Create & enrich for one Account from Salesforce. With Salesforce and ACE connected, configure Lead Enrichment Mapping Configs in Co-sell settings. The scheduled workflow selects, checks, creates, enriches and records; a mapping from the former Leads-and-Contacts workflow must be replaced with an Account mapping. This creates AWS leads, unlike Auto-Enrich Referrals or CRM intelligence-signal enrichment.
The Account mapping documentation specifies the additional rules:
| Control | Documented behavior |
|---|---|
| Required company data | Name, website, industry and convertible country; state for US Accounts. Industry Value Mapping must cover every source value. Website is read from the Account, never fixed |
| Contact | Most recently active contact with an exact website-domain match; newest-created breaks a tie. A Primary contact Lookup-to-Contact overrides that choice if it belongs to the Account and has an email; otherwise domain matching applies |
| Required contact data | First name, last name, email and business title; no guessed contact. A subdomain such as partner.acme.example does not match acme.example |
| Other mapping | City, postal code, company phone, use case and business problem are optional. Country names or codes such as United States and USA convert to US |
| Filter and validation | An empty Sync Filter selects nothing. Validate reads the filter without creating leads and counts missing websites, missing contact emails and absent domain matches among the most recently created matching Accounts |
| Schedule | Off by default; when enabled, runs at 03:15 UTC, up to 500 Accounts per organization per run, carrying a backlog into later days |
| Repeat submissions | Scheduled enrichment submits each Account once, whatever its outcome. Manual re-enrichment becomes available after 30 days, including no-data and failed results |
Results appear in Metrics > Logs → Lead Enrichment. Rejected means creation did not happen; complete missing company or contact fields, fix industry mapping, or resolve UNTRANSLATED_COUNTRY_VALUE. AWS’s PARTNER_LEAD_CREATION_NOT_ENABLED needs AWS enablement; ENGAGEMENT_ALREADY_EXISTS means exclude the Account or contact support. Already enriched needs no correction.
After creation, outcomes are Enriched, No data or Failed. The lead starts accepted, qualification Open, source Salesforce Account (enrichment); work it through Research and Qualified before Convert to Opportunity. The lead displays readiness, solution category and sub-category and AWS insights; Salesforce shows Readiness, MP Engagement and Solution Fit beside the Account. The Salesforce guide covers on-demand enrichment even with automation off.
The limits are specific: this lead sync reads Salesforce Accounts only and creates AWS leads only. It cannot supply insights AWS does not return or enable lead creation for an ineligible account. Your team owns data quality, contact selection and qualification; co-sell automation does not remove those responsibilities.
Frequently asked questions
How do AWS-shared leads differ from leads we create?
AWS-shared leads arrive as invitations, which you accept or reject within five business days. Contact details become visible only after acceptance. Creating partner-originated leads from your account list is a separate outbound workflow; it does not begin with an AWS invitation.
Sources
Primary sources for the platform rules cited above. Last verified September 24, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- AWS What's New: AWS Partner Central now provides lead enrichment and prospecting — Posted June 15, 2026 and available on posting: leads uploaded in the console or through the API, AWS-sourced and partner-sourced leads enriched, eligibility for the Partner Greenfield Program, Pioneer Credits and the Partner-Led Sales Motion, and availability to ACE-eligible partners
- AWS Partner Central Sales Guide: Managing leads — Accepting, importing, enriching, updating and converting as separate actions on the Leads page, and conversion once a lead reaches the Qualified stage
- AWS Partner Central Sales Guide: Importing leads — Import leads creates partner-originated leads through ACE from a CSV of 1 to 100 rows; every template column and its format; field validation and its common causes; same-day duplicate prevention; the failed-records file; enrichment as a step after import
- AWS Partner Central Sales Guide: Enriching leads — Enrich leads as a batch action on the Leads tab, the Enriched lead batches tab, the three readiness actions with a High, Medium or Low confidence level, and the four AWS insights
- AWS Partner Central Developer Guide: Manage leads using the AWS Partner Central Selling API — API enrichment is an asynchronous prospecting task of up to 100 leads, each processed independently
- AWS Partner Central Sales Guide: Receiving leads shared by AWS — AWS-shared lead invitations are accepted or rejected within a 5-business-day window, and contact information is visible only after acceptance
- AWS Marketplace Seller Guide: Adding private offer and demo request buttons — Buyer requests without sufficient business context are shared with the seller as leads, which can then be enriched
- AWS What's New: AWS Partner Central introduces Partner Lead Prospecting — Posted July 9, 2026: AI-generated sales plays, call scripts and email outreach for ACE-eligible partners, building on lead enrichment
- AWS Partner Central Sales Guide: Using agents for lead prospecting — The prospecting actions unlock on a lead only after it has been enriched
- Fours docs: AWS Partner Central Leads — Fours behaviour: the Account field map, the contact rule, the industry map, the sync filter, the 03:15 UTC run, 500 Accounts per run, each Account once, outcomes and rejection reasons
- Fours docs: Work AWS Co-Sell Leads — Fours behaviour: Create & enrich on a single Account from Salesforce, the 30-day re-enrichment window, and the lead card beside the Account
- Fours docs: Referral Automations — Fours behaviour: lead enrichment kept apart from Auto-Enrich Referrals and CRM intelligence-signal enrichment
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn