LocaliQ

LocaliQ is Gannett’s digital marketing platform for local businesses. AFI sends lead data from WordPress form submissions directly to your LocaliQ lead intake endpoint.

LocaliQ’s public API (api.localiqservices.com) is read-only for reporting. Lead intake is handled through a per-account Lead Intake URL and Bearer token that LocaliQ’s onboarding team provisions for you. There is no self-serve API key dashboard for lead submission.

What you’ll need

• An active LocaliQ account.
• A Lead Intake URL and Bearer token, provided by your LocaliQ account team.
• The Advanced Form Integration plugin installed and activated.

Save your LocaliQ credentials

1. Ask your LocaliQ account team for a Lead Intake URL and Bearer token. These are provisioned per account and are not available in a self-serve dashboard.
2. In WordPress, go to AFI → Settings → LocaliQ.
3. Paste the full Lead Intake URL (including any per-account path segments) into the Lead Intake URL field.
4. Paste the Bearer token into the Bearer Token field.
5. Click Save Changes.

AFI stores these credentials securely and uses them to POST JSON lead data to your intake URL with an Authorization: Bearer {token} header.

Create the integration

1. Go to AFI → Add New.
2. Give the integration a name, for example Contact Form to LocaliQ.
3. Under Trigger, pick your form plugin and the specific form.
4. Under Action → Platform, select LocaliQ.
5. In Task, choose Submit Lead.
6. Select the saved LocaliQ account.
7. Map your form fields to the LocaliQ lead fields (see below).
8. Optional: configure Conditional Logic to limit which submissions are sent.
9. Click Save Integration.

Tasks supported

Submit Lead

POSTs a JSON payload to your configured LocaliQ Lead Intake URL. The request includes an Authorization: Bearer {token} header and a Content-Type: application/json header. Email is required; all other fields are optional.

Request payload structure

AFI structures the submitted data as follows before sending:

{
  "contact": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "jo**@*****le.com",
    "phone": "+15551234567",
    "postalCode": "90210"
  },
  "message": "Interested in your services",
  "source": "website",
  "campaignId": "CMP-12345"
}

Empty fields are omitted from the contact object via array_filter. The source field defaults to AFI if not mapped.

Conditional logic example

Only send leads to LocaliQ when the form’s hidden source field equals “paid_search”. Organic submissions are skipped, keeping your LocaliQ lead pool clean.

Troubleshooting

Leads not arriving in LocaliQ

• Go to AFI → Log and check the most recent entry for the HTTP response code and body.
• Verify the Lead Intake URL and Bearer token are correct in AFI → Settings → LocaliQ.
• Make sure the Email field is mapped. AFI will not send a lead without an email address.

“LocaliQ intake URL or Bearer token missing”

This error appears in the log when the credentials have not been saved. Go to AFI → Settings → LocaliQ and enter both the Lead Intake URL and Bearer token.

401 or 403 response

The Bearer token may have expired or been rotated. Contact your LocaliQ account team for a new token and update it in AFI settings.

Notes and caveats

• LocaliQ does not expose a self-serve API for lead submission. The Lead Intake URL and Bearer token must be obtained from your account team.
• The intake URL may include per-account path segments. Paste the full URL exactly as provided.
• For lead source attribution, map {{utm_source}} or a form field to the source field.

Related docs

• ActiveCampaign
• Brevo
• Reading the Log
• Conditional Logic