xConnect Collection service

Current version: 10.0

The xConnect Collection service performs the following functions:

  • Receives contacts and interactions, either individually or in a batch.

  • Allows reading of contact and interaction data by ID or identifier.

  • Supports data extraction.

The xConnect Collection service can be accessed using the xConnect Client API or another API that consumes the oData service.

Supported infrastructure

You can host the xConnect Collection service on:

Refer to the Sitecore compatibility table for compatible versions.

Reference structure

The xConnect Collection service has its place in the Sitecore reference structure. It can be referenced by other roles, and it can also reference other roles.

Illustration showing the xConnect Collection service's place in the Sitecore reference structure.

Referenced by

The xConnect Collection service is referenced by the following roles:

References

The xConnect Collection service references the following roles:

Storage roles

Role name

Connection string name

Port

Type

Notes

xDB Collection database

collection

1433

SQL

The port number depends on your SQL Server configuration.

Marketing Automation database

xdb.marketingautomation

1433

SQL

The port number depends on your SQL Server configuration.

xDB Processing Pools database

xdb.processing.pools

1433

SQL

The port number depends on your SQL Server configuration.

Message Bus

messaging

1433

SQL

The port number depends on your SQL Server configuration. If you install Sitecore using SIF, SQL is the default provider.

443

Azure Service Bus

If you install Sitecore on Azure, Azure Service Bus is the default provider. Azure Service Bus is available in 9.2 and later.

Privacy and security

The xConnect Collection Service handles personal data in the following ways:

Note

Any client application with access to xConnect has access to personal data, even if the application does not access or use personal data.

Assumptions

  • All personal data written to and returned from the xConnect Collection service has valid and active data subject consent.

  • If required, client applications reading or writing data have explicit consent to do so.

Do you have some feedback for us?

If you have suggestions for improving this article,