Pull domain name of user for tracking within org

[Andrew_Blackburne]

I'm apart of an organization and am wondering if there is a way to pull the domain of the individual applying a snippet from a team folder.

Context:
We're attempting to track snippet application for multiple reasons to be forwarded to a google form (and eventually a google doc). The roadblock we're running into is tracking who is applying the snippet. Is there a code already in place for this?

If not, this function would be extremely useful to have access to

Thank in advance!

[Cedric_Debono_Blaze]

Hi @Andrew_Blackburne

Org accounts allow you to set up user properties.

To do this:

1. Navigate to the "Members" section of your org dashboard
2. Click on the gear icon next to member properties
3. Set up whatever properties you need

One way you could implement such a workflow is to insert the user property inside every snippet, and then use {urlsend} to send that information to a pre-populated google form as explained in the post below:

Saving Snippet Forms to Google Spreadsheets

Text Blaze can use the {urlsend} to save data when you use a snippet. This data can include anything you use in your snippet such as form values. The following instructions outline how to use this command to save data to a Google Form and Google Spreadsheet. Step 1: Create Your Snippet We'll create a simple order form where we enter the name of the company purchasing our product and the size of the product they purchased. Order Summary: Company name: {formtext: name=Company} Product Size: …

[Andrew_Blackburne]

Already well acquainted with the URL send feature. Which is amazing btw!
Checking those settings out now! Thank you so much

[scott]

For domain names of the user you don't need to configure any properties. The {user: email} command will include the user's email and you can get the domain name like so:

{=split({user: email}, "@")[2]}

You can learn more here:

{user}

[Cedric_Debono_Blaze]

@Andrew_Blackburne - Scott's solution is probably a lot more practical than mine. You should try that first.

The solution I proposed might be a good fit in cases where you wanted to have a unique identifier for each user, which might be cumbersome if you have many of them.

Let us know how this works out for you

[Andrew_Blackburne]

This actually answers my next few questions!
Way to kill 3 birds with one stone

[Cedric_Debono_Blaze]

Awesome!