Landing Pages Archives - gettectonic.com - Page 3
Pardot Forms Unleased
08Feb

Pardot Forms Unleashed

Setting up and maintaining Pardot forms is generally straightforward using the point-and-click Pardot form builder. Pardot Forms Unleashed. You can select the fields you want prospects to complete, define completion actions upon form submission, and then integrate the form seamlessly onto your website or landing pages. However, there are some nuances, or “gotchas,” with Pardot forms that can complicate your campaigns, impact reporting accuracy, and affect data quality. Here are some lesser-known tips to navigate these challenges effectively: By understanding these nuances and best practices, you can effectively leverage Pardot forms to drive marketing initiatives while maintaining data integrity and campaign effectiveness. Pardot Forms Unleased. Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Service Cloud with AI-Driven Intelligence Salesforce Enhances Service Cloud with AI-Driven Intelligence Engine Data science and analytics are rapidly becoming standard features in enterprise applications, Read more

Read More
February 8, 2023in Salesforce
snowpark container services
08Feb

Snowpark Container Services

Snowpark Container Services is a fully managed solution designed to simplify deploying, managing, and scaling containerized applications within the Snowflake ecosystem. Key Features Benefits of Snowpark Container Services in Native Apps Integrating Snowpark Container Services into Snowflake Native Apps enables developers to create solutions for various use cases, including: Developers benefit from Snowflake’s Native Apps Framework safeguards, which ensure secure and efficient operations. Development Workflow for Snowpark Container Services Here’s a quick guide to the development cycle for building and deploying containerized services within Snowflake. 1. Develop Code Locally 2. Build and Push an Image 3. Provision Resources 4. Deploy and Test Services Getting Started To build containerized applications with Snowpark Container Services: For a deep dive into architecture and workflows, explore Snowflake’s guides and tutorials on Snowpark Container Services and Native Apps. The Snowflake Native Applications Framework allows developers to package Snowflake features into standalone applications that can be installed across multiple accounts. This framework now supports advanced features for managing resource provisioning and deploying container services. Below is an overview of how to integrate container services into a Native App. Key Components 1. Manifest File The manifest file defines the configuration and setup properties for the application, including: Example Manifest File: Specifying Container Images yaml Copy code manifest_version: 1 version: name: V1 label: “Version One” comment: “The first version of my amazing Snowflake Native App” artifacts: readme: readme.md setup_script: scripts/setup.sql container_services: images: – /provider_db/provider_schema/provider_repo/server:prod – /provider_db/provider_schema/provider_repo/web:1.0 Here: Setting a Web UI as the Landing Page For apps with a web UI, specify a default_web_endpoint field to make the UI the landing page. yaml Copy code default_web_endpoint: service: ux_schema.ux_service endpoint: ui Here, service corresponds to the name defined in the CREATE SERVICE command, and endpoint refers to the service’s endpoint in the specification file. Using Streamlit as a Landing Page Alternatively, you can specify a default_streamlit field to use Streamlit as the landing page. Note: default_web_endpoint and default_streamlit are mutually exclusive—you can only use one. 2. Setup Script The setup script executes during the application installation and upgrade processes. It contains SQL statements for creating: Resource Provisioning for Snowpark Container Services The setup script also includes logic for provisioning resources like compute pools. However, these provisioning procedures are executed post-installation to ensure the consumer has granted the necessary privileges. Managing Compute Pools and Privileges Consumer-Controlled Resource Provisioning A foundational principle of the Snowflake Native Apps Framework is that consumers maintain full control over the resources the application accesses. This includes compute resources. Privileges Required To enable an application to provision resources, specific privileges must be requested in the manifest file: Example Privileges in the Manifest File yaml Copy code privileges: – CREATE COMPUTE POOL description: “Enable application to create its own compute pool(s)” – BIND SERVICE ENDPOINT description: “Enables application to expose service endpoints” Note: These privileges are not granted by default. The installation user may need to request them from another user with the appropriate permissions within the organization. By wrapping container services into a Snowflake Native App, developers can: This approach ensures that both providers and consumers retain control over their resources and data, while maximizing the capabilities of Snowflake Native Apps. Managing Privileges and Deploying Services in Snowflake Native Apps Once a Snowflake Native App is installed, consumers can grant the necessary privileges through various supported mechanisms. Here’s an overview of how to configure privileges, deploy services, and manage app components effectively. Granting Privileges 1. Snowsight UI Configuration Snowflake Native Apps with Snowpark Container Services provide a custom Snowsight configuration UI. When privileges are granted via this UI, it triggers the app’s grant_callback procedure specified in the manifest file. This procedure receives a list of privileges as input, making it ideal for initiating resource provisioning, such as creating compute pools. For containerized apps, this is the recommended approach. Example Manifest Configuration: yaml Copy code manifest_version: 1 configuration: log_level: debug trace_level: always grant_callback: setup.grant_callback 2. Streamlit Integration Using Snowflake’s Permissions SDK, developers can create Streamlit-based pop-ups to request privileges. After privileges are granted through the pop-up, resource provisioning can begin. Specify Streamlit as the landing page in the manifest using the default_streamlit field. This configuration allows Streamlit to invoke the necessary resource provisioning procedures. 3. SQL Worksheet Consumers preferring SQL-based interaction can grant privileges and execute resource provisioning procedures directly through the SQL worksheet. Example Grant Callback Procedure: sql Copy code CREATE OR REPLACE PROCEDURE setup.grant_callback(privileges ARRAY) RETURNS STRING AS $$ BEGIN CREATE COMPUTE POOL IF NOT EXISTS backend_compute_pool MIN_NODES = 1 MAX_NODES = 1 INSTANCE_FAMILY = CPU_X64_XS; CALL services.start_backend(‘backend_compute_pool’); RETURN ‘Callback successful’; END; $$; GRANT USAGE ON PROCEDURE setup.grant_callback(ARRAY) TO APPLICATION ROLE app_public; This procedure creates a compute pool and then calls another procedure to set up services within the pool. Deploying Services Once compute pools are created, the application can deploy one or more services. Scenario 1: The App Has All Required Resources If the app has everything it needs, it can directly execute CREATE SERVICE commands in the grant_callback procedure to set up its services. For services requiring warehouses, the app can request the CREATE WAREHOUSE privilege in the manifest and create warehouses as needed. Scenario 2: The App Needs Additional Consumer Resources If the app requires additional objects (e.g., external access integrations or secrets) from the consumer, references can be used. A reference includes a register_callback procedure that binds the required resources. This procedure can also trigger service creation after the reference is bound. Example Register Callback Procedure: sql Copy code CREATE OR REPLACE PROCEDURE v1.register_single_callback(ref_name STRING, operation STRING, ref_or_alias STRING) RETURNS STRING LANGUAGE SQL AS $$ BEGIN CASE (operation) WHEN ‘ADD’ THEN SELECT SYSTEM$SET_REFERENCE(:ref_name, :ref_or_alias); CASE (:ref_name) WHEN ‘external_access_backend_reference’ THEN CALL services.start_service_with_egress(); WHEN ‘secret_reference’ THEN CALL services.start_service_using_secret(); END CASE; WHEN ‘REMOVE’, ‘CLEAR’ THEN SELECT SYSTEM$REMOVE_REFERENCE(:ref_name); ELSE RETURN ‘Unknown operation: ‘ || operation; END CASE; RETURN ‘Operation ‘ || operation || ‘ succeeds.’; END; $$; This procedure: Packaging Service Specifications Service creation requires specification files, which must be included in the app package (typically alongside the manifest.yml). These files define the service

Read More
February 8, 2022in Data, Snowflake
salesforce marketing cloud interaction studio
28Apr

Ampscript

What is AMPscript used for in Salesforce? What is its purpose? AMPscript is a useful scripting language that you can use across emails, landing pages, SMS, and push notifications in Salesforce Marketing Cloud Builders. AMPscript is Marketing Cloud‘s proprietary scripting language for advanced dynamic content in emails, landing pages, SMS, and push messages. Why use Marketing Cloud AMPscript? AMPscript allows you to extend Marketing Cloud functionality beyond its out-of-the-box capabilities because you can develop code and custom solutions, tailored to your own specific needs and requirements. What are some functions you can perform with AMPscript? Types of Functions in Marketing Cloud AMPscript: What are advantages of AMPscript compared to Ssjs? For the web developer who are new to both languages, for them AMPscript has a shorter learning curve compared to SSJS. AMPscript should be preferred for simple inline personalization, which includes content like name, salutation and simple IF ELSE loops. Using AMPscript To use AMPscript, you insert it into the content body of your messages at the point where you want it to render. When you send a message that contains AMPscript, Marketing Cloud Engagement interprets the code and substitutes it with the output of the AMPscript function. 3 Way to Add There are three ways to add AMPscript code to your content: by using inline code, by adding code blocks, or by using tag-based scripting. The first two of these methods use special delimiters to denote the beginning and ending of the code that you want Marketing Cloud Engagement to interpret. In the third method, you delineate the AMPscript code with <script> tags. When you close an AMPscript block, use the same type of closing delimiter as you used to open the block. For example, if you open a block using tag-based scripting, you can’t close it by using the closing code block delimiter. Use the %%= and =%% delimiters to add AMPscript code inline with your content. Inline AMPscript is frequently used within HTML tags to dynamically populate the content of a message. In this basic example, a section of AMPscript is included inline within an HTML <p> tag. You can also include multi-line blocks of AMPscript code in your messages. Use the %%[ and ]%% delimiters to begin and end a code block, respectively. With a code block, you can define multiple variables and execute multiple functions. Code blocks use the syntax shown in this example. Tag-based syntax for AMPscript standardizes the syntax used to declare AMPscript blocks with the syntax of Server-Side JavaScript (SSJS). This syntax makes it easier for developers to switch between AMPscript and SSJS. Like1 Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Service Cloud with AI-Driven Intelligence Salesforce Enhances Service Cloud with AI-Driven Intelligence Engine Data science and analytics are rapidly becoming standard features in enterprise applications, Read more

Read More
April 28, 2021in Salesforce Marketing Cloud
Smart Capture Forms as Marketing Cloud Journey Entry Source
23Nov

Smart Capture Forms as Marketing Cloud Journey Entry Source

Transforming your marketing strategy into a seamless journey for your customers has never been easier, thanks to the integration of CloudPages’ Smart Capture forms with Journey Builder Entry Events. By leveraging this innovative feature, you can effortlessly guide your audience through personalized experiences that drive engagement and conversions. Smart Capture Forms as Marketing Cloud Journey Entry Source. Crafting these dynamic forms is a breeze, whether you prefer the classic or Content Builder editor, embedded within your landing pages or microsites. However, to take advantage of this functionality, it’s essential to ensure that you have both Journey Builder and CloudPages at your disposal. If you’re missing either piece of the puzzle, a quick chat with your Relationship Manager can swiftly rectify the situation. Now, let’s dig into the mechanics of how this synergy works. To initiate customers into a journey, the data captured by Smart Capture forms must be securely stored in a designated data extension. This data extension, aptly named the Event Source data extension, serves as the reservoir from which contacts are seamlessly injected into your Journey Builder journeys. Remember, for this mechanism to function seamlessly, your Event Source data extension must be configured as sendable. Creating a Smart Capture Form within CloudPages is a straightforward process: Navigate to CloudPages and effortlessly drag the Smart Capture gear onto the content area of your chosen landing page or microsite.Establishing a Data Extension tailored for Smart Capture as a Journey Builder event is paramount. This dedicated data extension serves as the conduit for seamlessly integrating Smart Capture forms with Journey Builder Entry Events. Here’s how to get started: Create a marketing cloud data extension explicitly designed to handle Smart Capture data within the context of Journey Builder.These conditions are required for creating a data extension to use in a Journey Builder entry event. Choose Create from New.Enter a name and select Is Sendable? if you plan to use emails with your Smart Capture form or Journey Builder journey.On the Data Retention Policy step, keep the default setting and click Next. Add any fields you would like to capture. When adding an Email Address attribute, change the Data Type to EmailAddress as email address because email address is the primary key. Set Send Relationship to the Email Address attribute so it relates to Subscribers on Subscriber Key. Smart Capture Forms as Marketing Cloud Journey Entry Source For those seeking further clarification or guidance on integrating Smart Capture forms with Journey Builder Entry Events, our comprehensive FAQs offer valuable insights: My Smart Capture form used as the trigger event for my journey won’t submit. What’s happening?Ensure that you configured the re-entry option and default channel address in the journey settings. I can’t get my journey to execute?If your journey includes an email send there are 2 important steps to complete before the journey can be executed. Within Email Studio, open up your email and be sure to complete both the Content Detective and Validate steps. Complete these steps before a journey can send that email. Explore our FAQs section dedicated to illuminating the intricacies of utilizing Smart Capture forms as Journey Builder Events within CloudPages. With this powerful integration at your fingertips, you can orchestrate personalized customer journeys that captivate your audience and drive tangible results. Embrace the potential of CloudPages‘ Smart Capture forms within Journey Builder to elevate your marketing endeavors to new heights of success. Like1 Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Service Cloud with AI-Driven Intelligence Salesforce Enhances Service Cloud with AI-Driven Intelligence Engine Data science and analytics are rapidly becoming standard features in enterprise applications, Read more

Read More
November 23, 2020in Salesforce
Marketing Cloud Cloudpages
01Jun

Salesforce Marketing Cloud Cloudpages

Utilize the CloudPages builder in Marketing Cloud Engagement to effortlessly publish targeted marketing content across multiple channels. CloudPages, a feature within Salesforce Marketing Cloud, offers drag-and-drop tools and pre-built templates for creating and publishing landing pages, preference center pages, and more. Salesforce Marketing Cloud empowers efficient marketing processes and streamlined customer relationship management. It enables the creation of customer profiles and tracking of interactions across various channels, including email, social media, and web interactions. CloudPages facilitates the automatic saving of Smart Capture block data, addition of default content versions to multiple destinations, and the design and preview of content in the audience’s format. For customer experience, CloudPages ensures a seamless process where prospects view and convert on pages using capture forms, with their data instantly updated in relevant Data Extensions. They are efficiently added to Journey Builder flows and receive tailored marketing communications promptly. Organize information for specific destinations, such as landing pages or microsites, with a Cloud Pages collection. Landing pages, created with Cloud Pages, can include custom forms with Ampscript and can be embedded in emails and websites. CloudPages smart capture forms can be used as a Journey Builder Entry Event. The difference between landing pages and CloudPages lies in CloudPages being an application within Marketing Cloud that can publish to various destinations, including Landing Pages. Marketing Cloud Engagement, with the inclusion of Cloud Pages, aids in conversions by providing a drag-and-drop interface for easy creation of landing pages, eliminating the need for complex coding. To create a landing page in Marketing Cloud, navigate to Web Studio > Cloud Pages, create a new collection, and within it, click ‘Create’ and select ‘Landing Page.’ Building CloudPages is user-friendly, featuring a drag-and-drop interface with templated layouts, content blocks, and dynamic content options. It allows easy insertion of text, images, buttons, forms, and more. Salesforce Marketing Cloud differs from Pardot, with Pardot being closely integrated with sales on the Salesforce core platform, while Marketing Cloud operates as a separate application. Landing pages are still crucial, as research indicates that businesses with more landing pages tend to experience higher conversion rates. The term “landing page” refers to a campaign-specific page with a single call to action and no website navigation. Insider tips for using Cloud Pages include making content relevant with Dynamic Content blocks, avoiding information overload, ensuring mobile-friendliness, and experimenting with different page versions for optimal performance. Content updated September 2023. Like2 Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Service Cloud with AI-Driven Intelligence Salesforce Enhances Service Cloud with AI-Driven Intelligence Engine Data science and analytics are rapidly becoming standard features in enterprise applications, Read more

Read More
June 1, 2020in Salesforce Marketing Cloud
Salesforce Marketing Cloud Email Studio
13Feb

Salesforce Marketing Cloud Email Studio Explained

While Journey Builder guides your customers’ journey, Salesforce Marketing Cloud Email Studio empowers you with the tools needed to craft the email content for your campaigns and journeys. Featuring robust functionalities, Email Studio facilitates the creation of polished emails, offering customizable elements, scripting languages, and personalized real-time content. With Salesforce Marketing Cloud Email Studio, you can effortlessly build and send personalized emails, ranging from basic newsletters to intricate campaigns. It allows you to deliver various types of messages, including promotional, transactional, and triggered messages, while also providing tracking and optimization tools to enhance performance. What does Email Studio offer? Email Studio enables you to automate transactional communication and send personalized messages to specific target groups. It also supports the delivery of timely triggered messages aligned with customer journey milestones across digital channels. Effortlessly manage content across distribution channels by tagging, searching, and sharing within Email Studio. Additionally, the platform simplifies the creation of a comprehensive customer view by integrating data from any source through powerful contact management. What sets Email Studio apart from Contact Builder? Email Studio introduces the capability of creating folders within your Synchronized Data Extension folder, a feature not available in Contact Builder. This distinction allows you to organize your Synched Data Extensions efficiently by moving them into subfolders. Distinguishing Email Studio from Content Builder: Like1 Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Service Cloud with AI-Driven Intelligence Salesforce Enhances Service Cloud with AI-Driven Intelligence Engine Data science and analytics are rapidly becoming standard features in enterprise applications, Read more

Read More
February 13, 2020in Salesforce Marketing Cloud

Subscribe to our mailing list. Join our mail list to receive our newsletter

We'll keep you up to date with our latest news, insights, free resources, and much more.
Don't worry, we won't spam you.
gettectonic.com