تحميل

Company Integration Profiles

A Company Integration Profile, shown as a Merchant connection in Catalog Publishing, records a company's authorized account connection to an external channel. It identifies the destination Connector, merchant account, environment, region and authorized website, together with authorization and verification information.

It does not select catalog offers or publish products by itself. A Catalog Publication uses a connection together with selected offers, destination requirements and reviewed configuration.

For example, a company can validate its Google merchant connection before approving any listing. Another company needs its own authorized account context; it must not inherit access simply because both companies use the same Actualog Product.

Who configures and authorizes it

Integration Managers and Company Administrators with integration configuration authority maintain connection settings. Authorize Google access requires a Company Administrator's provider consent. An Integration Manager cannot replace that consent by typing a merchant account reference.

Credential references identify secrets stored through the configured secret service. They are not password fields. Do not paste passwords, access tokens or private keys into connection names, account references or Help requests.

Creating and checking a connection

  1. Open Data Integration → Catalog Publishing → Merchant connections and search existing records.
  2. Select Create new connection.
  3. Select the destination Connector by name and enter the genuine merchant account, data source, environment, region and merchant website.
  4. Supply the configured secure credential reference and save.
  5. A Company Administrator selects Authorize Google access and completes supported provider consent.
  6. Select Verify connection to check the account and supported provider setup.

Saving settings and completing provider consent are separate steps. Verification is also separate from authorization and from successful publication. Changes to critical connection information require renewed checks.

Common blockers

Google authorization requires an active supported connection and configured secure secret storage. Invalid or revoked credentials, unavailable provider configuration, an unverified account or incomplete developer registration prevent delivery. Unsupported destination operations must appear as unavailable rather than be presumed successful.

The publication's selected landing pages must belong to the authorized merchant website and describe the actual seller offer. A seller's website is not inferred from the manufacturer's website.

Ongoing maintenance

Review provider access, account references, website and environment when responsibilities change. Revoke or deactivate connections that should no longer deliver content. Queued work rechecks authority and connection validity before execution; an earlier approval does not make revoked credentials valid again.

Related topics: Channel Requirement Profiles, Catalog Publications, Channel Submissions.