Frequently Asked Questions

 Shortify.ing is a Salesforce Native Application designed to streamline the creation, management, and tracking of short links within your Salesforce Org. It offers robust data security, cost-saving benefits, and advanced features, empowering efficient management of short links. 

 Shortify.ing caters to clients across diverse industries such as healthcare, finance, retail, education, and more. Its seamless compatibility allows for easy configuration and management, enabling the creation of bulk and personalized short URLs either through its own user interface or integrated with other Salesforce applications like Marketing Cloud, Pardot, and more.

 Kindly refer our guide through following this link: http://cfsu.in/custom-domain-setup-guide

 For detailed information, please refer to this link: http://cfsu.in/config-experience-community

 It depends on how you are creating Short URLs. For example, if you use the REST service, then it consumes one 'super message; whereas if you use the Salesforce Standard way to create a custom URL, it will not cost you any super message for short link generation.

 Please find links for the installation Guide:

• For the Doc Version: http://cfsu.in/installationguide
• For the YouTube Video: http://cfsu.in/installation-guide-youtube

 Please use this link: http://cfsu.in/userguide 

Custom links are user-friendly short URLs that allow you to create concise links using a personalized string as an extension of the short domain. For instance, you can generate a short link such as https://abc.com/festival-offer, where 'festival-offer' is a custom or user-friendly text conveying the link's purpose to your audience in a clear and engaging manner.

 Yes, it depends on your selected plan and details submitted by you. For details, please contract with us at enquiry@shortify.ing 

 Yes, you can use Shortify.ing with any existing Site/Community/Digital Experience. Just make sure that this site/Community does not have an existing URL rewriter configured. 

 Yes, you can. For sample code that you can run in an anonymous window, please use this link: http://cfsu.in/apex-sample-code. 

 Yes, you can. For details, please refer to this link: http://cfsu.in/sub-flow-uses. 

 Yes, they are dynamic, and this feature is provided in our higher plan. 

 Yes, we provide a migration flow by which you can onboard your existing short URLs to the Shortify.ing System. 

 This depends on your selected plan. For details, please see our pricing page: https://shortify.ing/pricing. To increase this limit, contact our Sales Team.

 This depends on your plan and selected data source (CSV/Report/Campaign). Shortify.ing does not have a restriction on the number of Short URLs created, except for your chosen plan. However, Salesforce is a cloud-based application with its own restrictions, particularly for big data. Salesforce advises against using Master details if there is a probability of having more than 10,000 child records. Additionally, the lack of master-detail between our custom object Project and URL is another reason for this. In short, there should be no theoretical problem with Shortify.ing, but you may experience performance challenges due to Salesforce constraints. 

• The calling user must be a member of the Shortify.ing Department.
• Calling users must have at least read access on the parent Salesforce object. For example, if you are creating a Short URL for an Account/Contact/Opportunity, the caller must have at least read access on the respective record.
• Bucket name is required only for first-time calls for any given ID and SObject type. It is not used for 2nd and onward requests.
• SObjectId and SObjectType must match. For instance, if you are passing 'Account' as an SObjectType, then SObjectId must be a valid Account ID.
• Global methods use 'sObjType' and 'sObjectId' to identify URL buckets (cfsu__DataDump__c). Therefore, we cannot create multiple URL buckets (Container of Short URLs) for the same record.

 Yes, Shortify.ing differentiates between real clicks and clicks by bots. We do not count clicks by bots as link clicks.

•  No, we do not store any Shortify.ing data in any standard object. All our data are stored in custom object.
• Shortify.ing stores 'short URL and Click' data in your own Salesforce org using Custom Objects.

•  The system will send notification emails to the configured email ID, with details of created short links, if the data source type is CSV, Campaign or Report. If you use a proper organization-wide email, then there are very few chances for this email to end up in a spam folder.  
• This step is not mandatory for Shortify.ing functionality. Shortify.ing sends emails to users in certain cases, for example when you upload a CSV file and publish the project. After the completion of the process, Shortify.ing sends a status email to the publisher. 
• We recommend enabling it so that the user is notified with status of the projects created for short links.

 Most probably you have not properly configured an organization-wide email address, or the user's email ID is not verified. If the issue still persists, please reach out to us at support@shortify.ing 

 Yes, we have exposed global APEX methods, as well as developed a REST service, which you can use to create your own LWC component for creating Short URLs.

 There is no restriction when it comes to creating URLs. If your Salesforce Database and your purchase plan permits it, you can construct millions of URLs in any single day/month. However, if you're referring to link clicks/views, Salesforce has a restriction of 500K (Enterprise edition)/1000K (Unlimited edition) for sites. One page view (according to Salesforce) is considered as one link click/view in the view of Shortify. For more information on these limits, please refer to this Salesforce link: here. You can increase this limit with talking with Salesforce.

 Technically, Shortify.ing is capable of shortening links up to 4K characters, but some browsers do not support URLs larger than 2K. 

 Ensure that calling users are members of some Shortify.ing department. While adding users to the department, we add the required permission sets to the users.