Email Integration Monitor
Email Integration Monitor
Nylas Integration
For those who are using the Nylas Email Integration, there is visibility into the emails that are / are not matching to accounts within Naviga Ad.
Navigate to System Settings Module -> Integration -> Email Integration Monitor
A user will be displayed in this list if one or both of these settings is selected on their profile:
If the user enters an email address in the profile email integration tab (above screenshot) and authorizes connection to that email, then the other columns from the first screenshot will be populated as well.
The Nylas Sync State lets an admin know the status of the sync. See Nylas Email/Calendar Integration for details on the meanings of each Status. To refresh the sync status at any time, click the button "Refresh Nylas Sync State" above the table of user names and then click ok on the popup confirming you wish to revalidate the sync state. Any authorized connection will be checked and a grid will display showing the authorization status. Click ok after viewing and the main table will also be updated.
Under the email address in the "email to sync" column is a link to View Sync History for each user. Click on that link for a popup of all the matched and unmatched emails that have been processed. During testing and initial implementation of the Nylas email sync feature, users will often be looking for specific emails and asking questions about why something may or may not have shown up as linked to a customer account. This gives admins of the system additional visibility into the processed emails.
Emails will not have a link to read the text of the email for individual privacy reasons, but if it is a matched email, then authorized users can see the text of the email on the CRM Managers Rep Activity Screen or from the Customer and contact screens.
Email BCC / FWD Sync
In some cases, a media company may prefer to allow users to pick and choose which emails to sync by forwarding or bcc-ing emails to a monitored email address rather than using the Nylas integration, which will automatically scan the users inbox and sent mail (or other designated folder).
The plus side of using email BCC/FWD instead of Nylas is that there is more control for the users to pick and choose which emails to send into the system. The downside of using email BCC/FWD is that there is more control for the users to pick and choose which emails to send into the system. With the control being on the user, they can cherry-pick the positive emails and not sync if the client is unhappy with them. Allowing the user to pick the emails does allow them to keep the system more tidy though and eliminate syncing the clutter that might not be relevant to keep.
Navigate to System Settings Module -> Integration -> Email Forward and/or BCC Configuration
Select Yes to enable the bcc and/or forward integration. Once the gmail account is configured, it will be selected from the dropdown in step 3, below:
Click on the Connection Setup link from screenshot above.
Click New and give the connection an ID and a Description. The Connection Settings section will be filled in after following the steps below to create a gmail account and to get the Client ID and Client Secret from the Google Development Console.
To set up the email BCC/FWD integration, an admin must first setup the account which will be used for forwarding. We have standardized this using a google email address. If you are using G-Suite as your email system, you can use something like [email protected], or you can just create a free gmail account and use that. The important part is that you are able to get to the Google Developer Console to give your naviga ad instance oauth access to the mailbox to be able to actually sync the emails.
Follow these steps to enable the sync:
Create Gmail Account (If needed)
Navigate to Google Cloud: https://console.cloud.google.com/
Make sure upper right hand corner of webpage has email account selected – if not select and log into that email account:
If this is the first time using Google Cloud, you may have to agree to terms of service:
Select a project and choose New Project:
Give it any name and choose Create:
Once the creation is done, choose Select Project:
Under APIs and Services, choose OAuth consent screen:
Choose External and then Create:
Give the application a name (any name) and select your email address from the list:
Skip the app logo and App domain sections and then use any email address for Developer Contact and click Save and Continue:
Click Add or Remove Scopes:
Under the manually add scopes add these and click Add to Table: https://www.googleapis.com/auth/gmail.readonlyhttps://www.googleapis.com/auth/gmail.modify
Select ../auth/userinfo.email and openid from the top section (in addition to the two you added):
Click update at the bottom of the window and then Save and Continue. On the Test users screen you can leave it empty and choose Save and Continue:
Choose Back to Dashboard and then Publish App:
Once the pop-up is displayed to push to production, click Confirm:
Next click Library to go to the list of available APIs:
Type in Gmail and hit enter to search for the Gmail API:
Choose Gmail API and then click enable:
Next choose Credentials from the left menu and then Create Credentials at the top:
Choose OAuth client ID:
Chose Web application for the Application type.
Chose any name for the Name field. For Authorized JavaScript origins use the first part of the URL of the Naviga System. If there are test or dev systems with a different prefix, include them here as well. For example, our dev system the base URL is this: https://dev.navigahub.com yours will be your 3-digit site code where we have "dev" For the Authorized redirect URIs, you need to use the full URL or the screen you will be authorizing your connection on. For example, our dev system the full URL is this: https://dev.navigahub.com/ew/devdigital/general/setup/oauth_connections NOTE – the URL above is case sensitive so be sure it matches what you have in your browser URL. If EW or your 3-digit site code are capitalized, be sure to capitalize in the Authorized redirect URIs
Once you click Create you will get a pop-up with some important information:
In the Naviga Ad system you will need to go to the URL that you specified in the prior step and create a new connection:
Click save so the connection is saved just in case there is a problem with the authorization. When you are doing the authorize it needs to redirect to Google and then comes back to the Naviga Ad system. Click Authorize and then choose the email address (you may have multiple displayed if you have multiple Gmail accounts):
You may recall when setting up the OAuth Consent screen Google gave you a message about the App needing to be verified. Because the application has not been verified you will get a screen that looks like this:
Choose Advanced and then Go to navigahub.com (unsafe). This doesn’t make you any less safe, it is just google trying to protect your account. In this case you were the one that created the Google Cloud Account.
Next you will get the Google screen asking you for access to read and compose messages in this Gmail account. You need to select continue to proceed:
Assuming everything went ok, you should be back on the Naviga Ad screen with a green banner saying the connection was authorized. Just click save to make sure that everything was saved:
Once this has been enabled, users can start to BCC the created Gmail sync email account on emails sent to their clients. They can also forward emails received from their clients to that same email address and, if matched with an email in the system, the email will sync to the customer's account in the same way that the Nylas emails sync.
Back in the Email Integration Monitor, these BCC and FWD events will be displayed in the matched/unmatched tabs in the users sync history. Admins can tell how the email came into the system by looking at the source:
Last updated
Was this helpful?