Skip to main content

Understand Logs on Integrations

Learn how to access and understand integration logs in Swapcard to troubleshoot and audit data flows between systems effectively.

Swapcard records a log for each step of a connector's sync:

  • Start and end of the sync

  • Calls to the external system's API

  • Records imported into Swapcard, and records rejected with the reason

  • Mapped values that could not be applied

These logs are useful for:

  • Monitoring and troubleshooting connectors

  • Performing audits

Accessing Logs

In Swapcard Studio, open the integration and go to the Logs tab.

Each log shows its level, timestamp, event and message. Click the arrow at the start of a row to see the full log in JSON format.
Use the search bar to find a value in the messages and data, such as an email address or a Client ID, and filter the logs by level, date or event.

Common Error Logs

People

Email is required for profile [Client ID] to be created

This error occurs when the connector sends a user profile, that is a profile able to log in to Swapcard, without an email address. The email address is required for a user profile, so the record is not imported.

Email is invalid for profile [Client ID] to be created

This error occurs when the connector sends a profile with an email address in an invalid format, so the record is not imported.
Example of NOT valid email: john.doe@example

Swapcard can also reject an email address during the import with the error The email is not valid, for the same reason.

First name is required for profile [Client ID] to be created

This error occurs when the connector sends a profile without a first name. The first name is required to create a profile in Swapcard, so the record is not imported.

Last name is required for profile [Client ID] to be created

This error occurs when the connector sends a profile without a last name. The last name is required to create a profile in Swapcard, so the record is not imported.

This email is already used by profile id [Event Profile ID] in the event

This error occurs when the connector is trying to create a profile with an email address that is already used by another profile in the same event. The email address must be unique for each profile in an event.

Cannot change user of an existing community profile. Client Id [Client ID] is used by Event Profile Id [Event Profile ID] which is linked to email [Email].

This error occurs when the record's Client ID (external ID) is already used by a profile linked to another email address. A Client ID is unique across the whole community, so it can only belong to one person.
If that profile is not part of the event, the message shows Community Profile Id [Community Profile ID] instead of the event profile ID.
A profile can hold several Client IDs, and the message can show any of them, not necessarily the one of the record.

Check why the ID is shared before you resolve this error:

  • If the ID belongs to the same person, for example after an email change, turn on the Force conflicting ids option in the settings of the people object. The profile is then linked to the new email address.

  • If two different people share this ID in your source tool, fix the duplicate ID there. Do not turn on Force conflicting ids: both records would update the same profile, and its name, email address and the account used to log in would switch from one person to the other depending on the order of the records in each sync. Only the fields received are overwritten, the others (for example the photo or the biography) are kept, and no error appears in the logs. If the other person already has their own profile, that profile can lose its account and its badge codes.

If two people already share a profile:

  1. Give each person their own ID in your source tool.

  2. In Studio, open the profile and remove the external ID and the badge code of the person whose email address is not on the profile. Removing the ID of the person whose email address is on the profile has no effect: their record finds the profile again through their account.

  3. Remove that person's other information from the profile, for example their job title, photo or biography. A sync only overwrites the fields it receives.

  4. Run a sync. The person gets a new profile of their own.

If you want to understand more about client id, please refer to the connectors documentation or contact the Swapcard support team.

The barcode [Badge code] is already attached to the event profile id [Event Profile ID]

This error occurs when the record's badge code is already on another profile in the event. A badge code can only belong to one profile in an event, so the record is not imported.
It can appear after two people who shared a profile are separated: remove the badge code from the profile shown in the message, then run a sync again.

Exhibitor with internal ID [Exhibitor ID] does not exist on current event with internal ID [Event ID]. Cannot associate profile [Client ID]

This warning occurs when the connector links a profile to an exhibitor that is not part of the event. The profile is imported, but it is not linked to this exhibitor.

Sessions

Client ID is required for the session [Session title] to be created

This error occurs when the connector sends a session without a Client ID, so the session is not imported.

No title provided for the session with client ID [Client ID]

This error occurs when the connector sends a session without a title, so the session is not imported.

No valid start date for the session [Session title] — the mapped value is empty or not a recognised date format

This error occurs when the start date of a session is empty or in a format that Swapcard does not recognise, so the session is not imported. The same error exists for the end date: No valid end date for the session [Session title] — ….

End date is before start date for the session [Session title]

This error occurs when the end date of a session is before its start date, so the session is not imported.

Exhibitors

Invalid exhibitor email

This warning occurs when the connector sends an exhibitor with an email address in an invalid format. The exhibitor is imported without its email address.

Format

Each log is displayed in JSON format, with its fields in this order:

{    "event": "Log event type",    "connector_id": "Connector ID",    "connector_name": "Connector name",    "message": "Log message",    "connector_type": "Connector type",    "data": {        // Specific data related to the event; varies by event and is empty for some events.    }}

FIELD

DESCRIPTION

event

Type of the event, see Log Event Types

connector_id

Identifier of the connector

connector_name

Name of the connector

message

Description of what happened, also shown in the Message column

connector_type

Type of connector, for example eventbrite

data

Object holding data specific to the event type; {} when the event has none

The level and the timestamp of a log are shown in their own columns, not in the JSON:

COLUMN

DESCRIPTION

Level

Severity level of the event; can be debug, info, warn, error or fatal

Timestamp

Date and time of the event, in your browser's time zone

Log Event Types

Event Type

DESCRIPTION

sync_started

Marks the start of a synchronization process with Swapcard

sync_end

Indicates the end of a synchronization process with Swapcard

connection_successful

Recorded when a connection with an external system is successful

connection_failure

Logged when a connection with an external system fails

api_call

API calls made to the external system the connector is interacting with

insert_data

Records checked before they are sent to Swapcard: imported, or rejected with the reason

update_data

Records or values rejected for the update of an existing record in Swapcard

modify_data

Result of the import of each record into Swapcard: imported, or error with the reason

scan_badge

Recorded when a badge is scanned during the Visit connector sync process

mapping

Logged when mapped values could not be applied as configured in the field mapping

unresolved_sessions

Session codes received that match no session in the event

info

Other messages specific to a connector, for example a skipped record or an ignored webhook

Log Data Types

sync_started

Message: Starting synchronization at [Date]...

"data" : {  "startedAt": "2026-05-10T12:34:56.000Z"}

FIELD

DESCRIPTION

startedAt

Timestamp marking the start of sync, in UTC

sync_end

Message: Synchronization is ended. when the sync is completed, or Synchronization encountered an error (sync ID: [Sync ID]). with the error level when it failed. Give this sync ID to the Swapcard support team when you contact them.

"data" : {  "endedAt": "2026-05-10T13:34:56.000Z"}

FIELD

DESCRIPTION

endedAt

Timestamp marking the end of sync, in UTC

connection_successful and connection_failure

"data" : {  "id": "12345",  "message": "Error message returned by the external system"}

FIELD

DESCRIPTION

id

Identifier of the event in the external system

message

Error message returned by the external system; empty when the connection is successful

api_call

API calls are logged with the debug level, and with the error level when the call fails.
Messages: Send HTTP request to [URL]..., HTTP request ended for [URL], Report records for [URL] and HTTP request error for [URL].

"data" : {  "url": "https://api.example.com/data",  "method": "GET",  "body": null,  "isRetry": false,  "statusCode": 200,  "retryAttempt": 0}

FIELD

DESCRIPTION

url

The endpoint URL; credentials passed in the URL are removed

method

HTTP method used for the API call

body

Optional request body content; credentials are redacted

isRetry

Indicates if the call was a retry

statusCode

HTTP status code of the response; not present when the request is sent

retryAttempt

Number of times the call was retried

error

Error message, when the call fails

records

Records received from the external system, in Report records logs

insert_data

Logged before the records are sent to Swapcard:

  • with the info level for each record that will be created or updated: Profile [Client ID] will be inserted, Planning [Client ID] will be inserted (sessions), Exhibitor [Client ID] will be inserted or Items [Client ID] will be inserted;

  • with the error or warn level when a record or a value is rejected, see Common Error Logs.

"data" : {  "destination": "people",  "record": {    "email": "john.doe@example.com",    "firstName": "John",    "lastName": "Doe",    "clientId": "12345"  },  "error": "Optional error message"}

FIELD

DESCRIPTION

destination

Type of record: people, session, exhibitor or item

record

Main fields of the record: email, firstName, lastName and clientId for people; clientId, name, beginsAt and endsAt for sessions; name and clientId for exhibitors and items

error

Optional error message

update_data

Logged in a few cases when a record or a value is rejected for the update of an existing record. Most rejected records are logged as insert_data. The data has the same format as insert_data.

modify_data

Logged for each record sent to Swapcard, with the result of the import:

  • with the info level when the record is imported: Successfully imported profile [Email], Successfully imported planning [Session title], Successfully imported exhibitor [Name], Successfully imported item [Name], Successfully imported document or Successfully updated document;

  • with the error level when Swapcard rejects the record: Error while importing profile [Email], Error while importing planning [Session title], Error while importing exhibitor [Name], Error while importing item [Name], Error while importing document [Name] or Error while updating document [Name]. The reason is in error.

When a whole batch of records is rejected, a single error is logged, for example Error while importing people batch. Its record holds all the records of the batch, error lists the reasons and count gives the number of errors.

"data" : {  "destination": "people",  "operationType": "replaced_or_inserted",  "record": {    "input": {      "create": {        "email": "alice.johnson@example.com",        "firstName": "Alice",        "lastName": "Johnson"      },      "update": {        "email": "alice.johnson@example.com",        "firstName": "Alice",        "lastName": "Johnson"      },      "clientId": "98765"    },    "output": {      "id": "RXZlbnRQZW9wbGVfNDM4MTY4NDQ=",      "email": "alice.johnson@example.com",      "firstName": "Alice",      "lastName": "Johnson"    }  },  "count": 1}

FIELD

DESCRIPTION

destination

Type of record: people, session, exhibitor, item or document_or_link

operationType

Type of operation performed on the data: replaced_or_inserted

record.input

Data sent to Swapcard. For people, sessions and exhibitors, create is used when the record is new and update when it already exists. For people, it also holds the badge codes (barcode), the groups (groups) and the links to sessions and exhibitors

record.output

Record saved in Swapcard: its id, and for people the email, firstName and lastName. Only present when the record is imported

count

Number of records concerned: 1, or the number of errors when a whole batch is rejected

error

Optional error message

scan_badge (Only for Visit connector)

Messages: Retrieving barcode [Barcode] for event [Event ID] and community profile [Community Profile ID] when the scan is received, Barcode [Barcode] found for event [Event ID] … when the scanned person is found, or an error such as Partner connection with partner id [Partner ID] not found.

"data" : {  "barcodeScanned": "y1kcg0n8e6d",  "requester": {    "id": "37036466",    "firstName": "John",    "lastName": "Doe",    "email": "john.doe@example.com"  },  "connectionCommunityProfileId": "2395750"}

FIELD

DESCRIPTION

barcodeScanned

The scanned barcode value

requester.id

The community profile identifier of the requester

requester.firstName

The first name of the requester

requester.lastName

The last name of the requester

requester.email

The email address of the requester

requester.partnerId

The Visit partner identifier of the requester's exhibitor, when there is one

requester.exhibitorIds

The exhibitor identifiers of the requester, when no Visit partner identifier is found for them

visitorIdScanned

The Visit visitor identifier of the scanned person

connectionCommunityProfileId

The community profile identifier of the scanned person, when found

error

The error message, when the call to the Visit API fails

mapping

Logged once per sync and object, not once per record. The message names each field concerned, the number of records affected and one example value.

MESSAGE

LEVEL

DESCRIPTION

Mapped values skipped for [Object name]: …

warn

The values were not imported: the field cannot be imported by this connector, or the value is not a recognised date, a valid URL or a valid phone number

Mapped values altered for [Object name]: …

info

The values were imported but shortened, as they were longer than the field allows

Fields not overwritten when updating [Object name]: …

warn

These fields were not updated on existing records, as Overwrite when updating an existing record is disabled for them in the mapping

Example:

Mapped values skipped for Attendees: websiteUrl (from "website") — 12 records: the value is not a valid URL (e.g. 12345: "n/a")

For skipped values, data.error repeats the part of the message after the object name:

"data" : {  "error": "websiteUrl (from \"website\") — 12 records: the value is not a valid URL (e.g. 12345: \"n/a\")"}

unresolved_sessions (Only for Experient connector)

Message: [Number] show item code(s) in imported registrants' ShowItemList match no session in this event.

Logged with the warn level. The registrants are imported, but they are not linked to the sessions with these codes. Check that these sessions exist in the event with these codes as Client ID.

"data" : {  "sessions": ["SESSION-101", "SESSION-102"]}

FIELD

DESCRIPTION

sessions

Show item codes that match no session in the event

info

Other messages specific to a connector, for example a record skipped by the connector, an ignored webhook, or the number of records retrieved from the external system. The level shows how serious the message is.

"data" : {  "message": "Additional details"}

FIELD

DESCRIPTION

message

Optional additional details

Data Retention

Swapcard retains integration logs for a period of 30 days. After this period, the logs are automatically deleted.

Troubleshooting

If you encounter any issues with integration logs, please contact the Swapcard support team for assistance.

Did this answer your question?