Span name |
Description |
|---|---|
Ingesting data from: [input name] |
An event batch is ingested into mParticle from an input configuration. The span will indicate the specific input as one of your mParticle SDK configurations, the Events API, or a partner data feed. |
Span name |
Description |
|---|---|
Queueing data to bulk payload for: [module name] |
This span represents the process of queueing an outbound bulk payload for delivery to an output. This span occurs after a bulk payload has already been generated. |
Processing ingested event batches |
This span represents the entire process of ingesting and processing inbound data, including (but not limited to) the process of verifying data against a data plan, applying rules and filters, checking for data duplication, and handling user profile updates. |
Processing outbound bulk payload for: [module name] |
This span represents the time spent accumulating data in a bulk payload before it is forwarded to an output. Data is added to a bulk payload until some condition is met: either a condition defined in your output configuration, or a limit imposed by the output integration. This span occurs only once for each trace. |
Span name |
Description |
|---|---|
Loading and executing rules |
Any configured rules are executed on your data. A similar span is repeated for both input and output rules. You can determine if the span represents input or output roles by looking at where in the trace timeline the span occurs, and the script that’s executed before the data is forwarded. |
Span name |
Description |
|---|---|
Identifying destinations and initiating data forwarding |
This span represents the time spent finding any connected outputs that data should be forwarded to, and the process of initiating data fowarding to those outputs. |
Building outbound payload for: [module name] - [configuration] |
This span represents the initialization of forwarding data, either in real-time or in bulk, to an individual output. This span is repeated for each configuration of a single output. |
Forwarding payload to: [module name] |
This span represents the time spent actually forwarding data to an output. |
Forwarding real-time data to: [module name] - [configuration] |
Data is sent in real-time to an output. The span indicates the name and configuration of the output. |
Span name |
Description |
|---|---|
Executing identification request |
A request is made to identify a user. |
Searching for user profile |
mParticle searches for an existing user profile matching the provided user identifier. |
Selecting Identity Strategy |
mParticle selects the identity strategy configured for your account. |
Searching for user identifier |
mParticle searches the IDSync service for a user matching the provided identifier. |
Retrieving identification result |
The results of an identification request are retrieved from the identity database. |
Storing identification result |
The results of an identify call are stored in the IDSync service. |
IDSync Search Request |
A request to the Search endpoint in the IDSync API. |
IDSync Login Request |
A request to the Login endpoint in the IDSync API. |
IDSync Logout Request |
A request to the Logout endpoint in the IDSync API. |
IDSync Modify Request |
A request to the Modify endpoint in the IDSync API. |
Was this page helpful?