<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Forms AJAX Submission Endpoint in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Forms-AJAX-Submission-Endpoint/m-p/229147#M8043</link>
    <description>&lt;P&gt;&lt;A class="mention" href="https://community.hubspot.com/u/derek_gervais"&gt;@Derek_Gervais&lt;/A&gt; I too have the same questions as &lt;A class="mention" href="https://community.hubspot.com/u/mattdev"&gt;@mattdev&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Additionally, with the v2 endpoint, you could include pageId in hs_context and, while not documented, it would actually count those form submissions against a specified HubSpot landing page. This worked great for us because we could capture form metrics on landing pages even though we were using non-native forms. I understand this probably was not inttentionally supported to begin with, but it was massively valuable to us and is now sorely missed with the v3 endpoint. Would it be possible to bring this functionality back to v3?&lt;/P&gt;
&lt;P&gt;Without this and what &lt;A class="mention" href="https://community.hubspot.com/u/mattdev"&gt;@mattdev&lt;/A&gt; mentioned, we are debating whether we should move to v3 or stick with v2 and use custom contact properties to capture consent data, and then workflow rules to populate legal_basis.&lt;/P&gt;
&lt;P&gt;Thanks for your consideration,&lt;BR /&gt;
-Noa&lt;/P&gt;</description>
    <pubDate>Tue, 19 Jun 2018 15:38:27 GMT</pubDate>
    <dc:creator>nflaherty</dc:creator>
    <dc:date>2018-06-19T15:38:27Z</dc:date>
  </channel>
</rss>

