# Original source set to "Offline sources"

**URL:** <https://community.hubspot.com/t/original-source-set-to-offline-sources/13480>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [March 13, 2019, 10:09am UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480 "2019-03-13T10:09:45Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [March 13, 2019, 10:09am UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/1 "2019-03-13T10:09:45Z")

</div>

Hello!

I am currently deugging our Hubspot intergration and I am seeing the"_Orginal source"_ for contacts is set to _“Offline sources”_.

We’ve implemented an email wall on the website. After the user has filled in their email we do a client side identify call with the email to create the contact in Hubspot and later a server side API call using the Contacts API for the users that are using ad blockers. I’ve confirmed that the identify call correctly sent.

This results in a contact in Hubspot for which the "_Orginal source"_ is set to _“Offline sources”_ and the _"__Original source drill-down 1"_ for these contacts it is set to "_ANALYTICS"_.

Would you be able to explain why the "_Orginal source"_ is not set to channel stored in the associated cookie (Search, direct etc)?

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [March 14, 2019, 3:53pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/2 "2019-03-14T15:53:15Z")

</div>

Welcome, @tashbukholt.

If all cookies are enabled and the [identify function](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor) truly creates the contact record before the [Contacts API](https://developers.hubspot.com/docs/methods/contacts/create_contact), then I would _not_ expect records to have the _Original Source_ value “Offline Sources.”

That said, if the Contacts API created the contact record, then I would expect _Original source drill-down_ 1 to be “API” — not “Analytics.” (Though the change source would be “Analytics,” per [this screencast](http://recordit.co/eGEwulq7IP).)

Could you share links to a few contacts which are displaying this behavior?

---

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [March 14, 2019, 5:13pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/3 "2019-03-14T17:13:56Z")

</div>

Hi @IsaacTakushi,

Thanks so much for your response!

I also would have expected the _Original source drill-down_ 1 to be “API” if the Contacts API was creating the contact record. However in our case the _Original source drill-down_ 1 value is “ANALYTICS”, while the _Original Source_ value is “Offline Sources”.

Below I have provided links of a few contacts where I see this happening . Two of these are test accounts I created - for these accounts I can guarntee the cookies were enabled:

> **[HubSpot](https://app.hubspot.com/contacts/4075618/contact/101387901/)**

> **[HubSpot](https://app.hubspot.com/contacts/4075618/contact/99195901/)**

> **[HubSpot](https://app.hubspot.com/contacts/4075618/contact/101272001/)**

> **[HubSpot](https://app.hubspot.com/contacts/4075618/contact/101335601/)**

Please let me know if you need any additional information.

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [March 20, 2019, 2:40pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/4 "2019-03-20T14:40:16Z")

</div>

Apologies for the delayed response, @tashbukholt.

Thanks for sharing those examples!

I actually don’t see form submissions or `hutk`/usertoken values associated with any of those four contacts.

Instead, I believe these contacts were created through the [frontend-email\_wall\_submitted](https://app.hubspot.com/analytics/4075618/events/000006072933/edit) custom event, which seems to have been triggered via the [Events HTTP API](https://developers.hubspot.com/docs/methods/enterprise_events/http_api) due to the lack of page views and cookie values. If the event had been triggered in a browser with the [Events JavaScript API](https://developers.hubspot.com/docs/methods/tracking_code_api/javascript_events_api), I would expect to see an online _Original Source_ value (e.g. “Direct Traffic”) and a usertoken on the backend.

Does the Events HTTP API ring a bell with you or your team?

---

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [March 25, 2019, 1:48pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/5 "2019-03-25T13:48:31Z")

</div>

Hey Isaac,

Thanks so much for the update.

Great find! We are working on implementing a fix for the custom events that have been triggered via the Events HTTP API.

I will touch base again next week when we know how the fix it going.

Thanks again for the help!

Tash

---

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [March 27, 2019, 1:38pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/6 "2019-03-27T13:38:31Z")

</div>

Hi @IsaacTakushi ,

Our team has implemented a delay so that the custom event, frontend-email\_wall\_submitted, is only triggered after the identify function.

When I tested this the _Original source drill-down_ 1 is still set to analytics “ANALYTICS”, and the _Original Source_ value is set to “Offline Sources”. [This](https://app.hubspot.com/contacts/4075618/contact/106777601/) is the account I created for testing.

Do you have any further insight into this for us? Is there a way to see what event contacts were created through?

Thanks,

Tash

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [March 28, 2019, 9:19pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/7 "2019-03-28T21:19:23Z")

</div>

Hey, @tashbukholt.

Thanks for the update!

I can confirm that [this contact](https://app.hubspot.com/contacts/4075618/contact/106777601/) was created by the same [frontend-email\_wall\_submitted](https://app.hubspot.com/analytics/4075618/events/000006072933/edit) event as before.

However, the “Offline Sources” _Original Source_ and lack of usertoken on the backend still suggest you’re using the [Events HTTP API](https://developers.hubspot.com/docs/methods/enterprise_events/http_api). These requests can’t pass `hutk` cookie token values and thus will always create “Offline Sources” \> “Analytics” contacts.

Did you switch to using the [Events JavaScript method](https://developers.hubspot.com/docs/methods/tracking_code_api/javascript_events_api)?

---

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [April 2, 2019, 2:16pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/8 "2019-04-02T14:16:54Z")

</div>

Hi @IsaacTakushi ,

Thanks for the insight!

We are exploring a few different solutions at the moment.

But just to make sure we are on the right track, could you please share the exact requirements that are needed to ensure the _Original Source_ field does not show as “Offline Sources” ?

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [April 2, 2019, 3:08pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/9 "2019-04-02T15:08:48Z")

</div>

Sure thing, @tashbukholt:

**Don’t:**

- Use the [Contacts API](https://developers.hubspot.com/docs/methods/contacts/create_contact), as it cannot pass `hutk` cookie values.
- Use the [Events HTTP API](https://developers.hubspot.com/docs/methods/enterprise_events/http_api), as it also won’t pass cookies.

**Do:**

- Use either the [`trackPageView`](https://developers.hubspot.com/docs/methods/tracking_code_api/track_page_view) or [`trackEvent`](https://developers.hubspot.com/docs/methods/tracking_code_api/javascript_events_api) JavaScript functions after the [`identify`](https://developers.hubspot.com/docs/methods/tracking_code_api/identify_visitor) function. These will pass a `hutk` cookie to the new contact record.
- Alternatively, use [this Forms API endpoint](https://developers.hubspot.com/docs/methods/forms/submit_form_v3) and pass a `hutk` value directly in the `context` object.

---

<div class="post-metadata">

**Author:** ![tashbukholt](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tashbukholt/32/76793_2.png) [@tashbukholt](https://community.hubspot.com/u/tashbukholt)\
**Post date:** [April 4, 2019, 3:19pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/10 "2019-04-04T15:19:02Z")

</div>

Hey @IsaacTakushi ,

This information was extermely helpful, thank you so much!

We are currently working on implementing the Forms API endpoint - we will use that to pass a hutk value directly to the context object.

I will let you know how it goes!

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [April 4, 2019, 8:48pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/11 "2019-04-04T20:48:13Z")

</div>

Glad to hear it, @tashbukholt!

---

<div class="post-metadata">

**Author:** ![bmauger](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bmauger/32/66643_2.png) [@bmauger](https://community.hubspot.com/u/bmauger)\
**Post date:** [June 29, 2023, 2:10pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/12 "2023-06-29T14:10:06Z")

</div>

Hi @IsaacTakushi - the “Forms API endpoint” link is taking to a 404 page. Is there a new page for this or any updates to the workarounds here since your post back in 2019. Thank you very much.

---

<div class="post-metadata">

**Author:** ![OGruzdyn](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ogruzdyn/32/25270_2.png) [@OGruzdyn](https://community.hubspot.com/u/OGruzdyn)\
**Post date:** [December 28, 2021, 7:00pm UTC](https://community.hubspot.com/t/original-source-set-to-offline-sources/13480/13 "2021-12-28T19:00:01Z")

</div>

what does it means when “contact was greated from Offline Sources from API”? I have google ads and facebook ads connected to my hubspot but only on some contacts i’m seeing which campaign the contact came from and from other contacts, it shows “offline sources” even though i’m thinking they still saw the fb ad and signed up to my list. What is there another way to confirm the source of the contact? I can’t seem to figure out how to set up the GCLID.
