Skip to main content
Contributor I
August 12, 2026
Solved

Job title - internal alerts

  • August 12, 2026
  • 3 replies
  • 84 views

Hello :)

 

I have set up a few forms with internal alerts that have all worked fine, except for this one needs to have job title included in the alert. I have tried all of these: job_title {{ person.job_title }} or {{ person|lookup:"job_title" }}.

 

None of them work, the final one puts in “None”, but the form field “Job Title” is mandatory and is lined up with the already set property “ job title”. I can’t work out where I am going wrong, as if you visit the profile of the form submitter, their job title is clearly there. 

 

Anyone else had anything like this and can advise?

 

Thanks!

Best answer by Temi O.

Hi there ​@charlsmithx! The most likely issue is that “Job Title” is the field label, not necessarily the exact profile property name Klaviyo needs in the tag.

Personalization is case- and space-sensitive, so I’d recommend opening a submitted profile and copying the property name exactly as it appears there.

If the form is mapped to Klaviyo’s standard Title property, try:

{{ person|lookup:'Title' }}

If it is a custom property named job title, try:

{{ person|lookup:'job title' }}
 

Also, if the internal alert is the first step after a form or list submission, try adding a short delay before the alert and test with a brand-new profile. That can give Klaviyo time to save the form response before the alert tries to read it. You can find more detail in Klaviyo’s personalization reference.

If the exact property name and a short delay still result in “None,” Support would be the best next step so they can review the form submission and alert setup together.

 


Temi@Klaviyo

3 replies

Temi O.
Community Manager
Temi O.Answer
Community Manager
August 14, 2026

Hi there ​@charlsmithx! The most likely issue is that “Job Title” is the field label, not necessarily the exact profile property name Klaviyo needs in the tag.

Personalization is case- and space-sensitive, so I’d recommend opening a submitted profile and copying the property name exactly as it appears there.

If the form is mapped to Klaviyo’s standard Title property, try:

{{ person|lookup:'Title' }}

If it is a custom property named job title, try:

{{ person|lookup:'job title' }}
 

Also, if the internal alert is the first step after a form or list submission, try adding a short delay before the alert and test with a brand-new profile. That can give Klaviyo time to save the form response before the alert tries to read it. You can find more detail in Klaviyo’s personalization reference.

If the exact property name and a short delay still result in “None,” Support would be the best next step so they can review the form submission and alert setup together.

 


Temi@Klaviyo

Contributor I
August 18, 2026

Hello!

Thank you very much for the response. Unfortunately now I can’t even try it, if I try to save any personalisation within an internal alert I get a “network error” which I do not get when I write plain text. So can’t be a connection issue if somethings save and others don’t! Will have to look to support, thank you :)

Temi O.
Community Manager
Community Manager
August 20, 2026

Okay sounds good! If you’re unable to connect with Klaviyo support, let me know and I can help. Hope this gets resolved soon for you! 
 


Temi@Klaviyo