# Why do external systems write to Processing fields rather than directly to the Engagement Object?

This approach leverages the existing data flow patterns that marketing automation platforms already use to write to Lead and Contact objects. We build on these established processes to capture interaction data.

Writing directly to the Engagement object would require external systems to handle complex logic around:

* Determining if an Engagement should be an Activation or Influencing Engagement
* Establishing proper relationships with existing records
* Managing data validation and business rules
* Handling edge cases and error scenarios

By using Lead and Contact Processing Fields as an intermediary, we keep this complex logic in Salesforce where it belongs, while allowing external systems to continue using their standard integration patterns.

For more details on how this data flows through the system, see [Processing, RAW, and Reporting Fields Explained](https://help.integrousanalytics.com/v1/docs/processing-raw-and-reporting-fields-explained).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.integrousanalytics.com/faqs/why-do-external-systems-write-to-processing-fields-rather-than-directly-to-the-engagement-object.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.