

1. Your team communicate with our technical integration team (targetconnect.integrations@groupgti.com) providing the following information:
- Your chosen email addresses, we require up to three pieces of information here:
1. Your 'From Address' (this is the address that users will receive emails from): ie future@careers.university.ac.uk
2. Your 'Reply-to Address' (this is the address that the user will appear to be responding to). This can be left blank if you only intend to send emails from this address, or often it is the same as your 'From Address'
3. Your 'To Address' (this is the recipient address for testing purposes only)With DKIM, we highly recommend that you utilise an email address with a subdomain ie future@careers.university.ac.uk for routing emails from a From Address - you can still use a Reply-to Address like future@uni.ac.uk .
- Any timescales you would like to adhere to
Technical Note: unless absolutely not an option, we utilise DKIM as a preferred solution to email routing. DKIM is now the industry standard and will help us to support ongoing service improvements. DKIM also gives a better service to your users as the email will appear to arrive directly from your institution and does not require a physical routing solution or an @targetconnect.net address. The remainder of these instructions will assume that the new email address utilises DKIM with a subdomain.
2. Your IT team will need to complete some DNS record work, details of which we will send to youDMARC is now a requirement for bulk senders using many major email providers, including Google and Yahoo. We strongly recommend that all institutions ensure an appropriate DMARC policy is in place for their sending domain, regardless of the volume of emails they expect to send. This helps meet receiving mail providers' requirements and reduces the risk of legitimate emails being rejected or classified as spam. Your institution's IT team should ensure that an appropriate DMARC policy applies to the sending domain as part of the email routing setup.
3. We will generate DKIM keys and publish them along with SPF on our side, you won't have to worry about adding anything to your own SPF recordWe use a 2048 bit DKIM key4. We will prepare our back end and test email delivery/signing for the subdomain we've set up5. We will set up the service addresses (from, reply-to, to address) on the platform as per your initial instructions6. Your institution should then conduct final mailing tests from the systemThroughout the process, our Technical Integration and Customer Success teams will be on hand to help

