# Hubspot Form Submission json (Source Data)

**URL:** <https://community.hubspot.com/t/hubspot-form-submission-json-source-data/87556>\
**Category:** APIs & Integrations\
**Tags:** forms\
**Created:** [August 15, 2023, 7:11pm UTC](https://community.hubspot.com/t/hubspot-form-submission-json-source-data/87556 "2023-08-15T19:11:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nathan951](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@Nathan951](https://community.hubspot.com/u/Nathan951)\
**Post date:** [August 15, 2023, 7:11pm UTC](https://community.hubspot.com/t/hubspot-form-submission-json-source-data/87556/1 "2023-08-15T19:11:06Z")

</div>

So when submitting a form, I see that the “pageUrl” is submitted as property: “hs\_latest\_source\_data\_1”

how can I set: “hs\_latest\_source\_data\_2”?

---

<div class="post-metadata">

**Author:** ![coldrickjack](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/coldrickjack/32/6684_2.png) [@coldrickjack](https://community.hubspot.com/u/coldrickjack)\
**Post date:** [August 15, 2023, 8:19pm UTC](https://community.hubspot.com/t/hubspot-form-submission-json-source-data/87556/2 "2023-08-15T20:19:33Z")

</div>

Hi @Nathan951,

Whilst it is possible to manually override the “Original and/or Latest Source” contact properties the “Original Source Drill-Down 1 and 2” and “Latest Source Drill-Down 1 and 2” contact properties are not editable in the UI or via the API. They’re set as read-only and set automatically by HubSpot using a number of different variables (see the table below or article [here](https://knowledge.hubspot.com/contacts/understand-source-properties))

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/2/e/2e3ff7a670d8442a83df4a598be4794b1e5397ed.png)

The above is ultimately how traffic is then categorised in the [Hubspot traffic analytics tool.](https://knowledge.hubspot.com/reports/understand-hubspots-traffic-sources-in-the-traffic-analytics-tool) Depending on what you are trying to do - the only potential workaround (but I’d be hesitant to go down this route) would be to leverage your own custom properties to capture this data. It would also require building your own custom reports to understand the source of traffic, it would also impact the content level reports for your forms, pages and emails along with other metrics in the portal.