Skip to content
CopyLoopCopyLoop Docs

Choose an integration

Choose an integration by the data source and outcome—not by copying everything into CopyLoop.

Web or mobile applicationUse a server-side contact webhook. First check: one real record is accepted and processed without blocking the app.
WordPress websiteInstall the Connector plugin. First check: CopyLoop sees the plugin version and a live visit.
Other websiteInstall the site-wide Connector snippet. First check: the source reports connected after a live page visit.
CopyLoop formPublish a hosted or embedded form. First check: a test submission updates the intended contact.
Existing WordPress formAdd the trusted form connection. First check: a test submit appears in Connector health.
WooCommerceComplete WordPress commerce setup. First check: a permitted test event appears in reporting.
SalesforceAuthorize and configure the CRM connection. First check: a controlled sync maps known records correctly.
Initial contact historyImport a CSV. First check: imported, rejected, and final contact counts are understood.

Keep the source of truth

Section titled “Keep the source of truth”

Your application, CRM, commerce platform, or website remains authoritative for the facts it owns. CopyLoop should receive the smallest useful set of profiles and events for communication, segmentation, automation, and measurement.

Do not give CopyLoop direct production-database access as the default way to connect an application. Use an authenticated, retryable application boundary.

Choose the trust boundary

Section titled “Choose the trust boundary”
  • A browser snippet uses a public site key, allowed origins, and consent-aware collection.
  • A WordPress plugin can use the public browser path and separate server-held credentials for supported trusted submissions.
  • An application webhook uses a private API key from a backend or serverless function.
  • Salesforce uses an authorized OAuth connection and configured field mappings.

Never put an application webhook API key or trusted form secret into browser code, page HTML, a mobile binary, or a public repository.

Separate profile sync from permission

Section titled “Separate profile sync from permission”

Creating a contact does not automatically establish permission to send marketing. Keep these questions separate:

  1. May this source send the profile or event to CopyLoop?
  2. May CopyLoop associate it with a person?
  3. May the customer use it for the intended marketing purpose?
  4. Is this particular person eligible for this message now?

Preserve the underlying consent or lawful-basis evidence in the responsible system and map only the state CopyLoop needs.

Start with one test

Section titled “Start with one test”

For any integration:

  1. document the source and owner
  2. map the minimum fields
  3. create one identifiable test record or event
  4. verify the source receipt and CopyLoop result
  5. test retry or duplicate behavior
  6. confirm no unintended audience or automation was activated
  7. expand volume only after the path is observable