Use of "External Tables" for temporary files
Platform: Outbound Marketing | 4 Comments 03.18.2009 Mike Corridan
Community Rank: 0.0 | Total Votes: 0
When an Epiphany Outbound system is not the only system used for campaigning at an organization, a quick and easy way to include those non-Epiphany campaigns into your solution is through the use of external tables.
During design, an external table can be created with very generic column and attribute definitions. You will need the customer number, or whatever your solution uses to uniquely identify your customers, and a couple of other elements such as campaign name, treatment and cell, and a couple of “empty” columns, one numeric and one character. Be generous on the size of the columns, but try to limit them total number to make loading and processing easier.
When non-Epiphany campaigns are created, once the file is obtained, you can load them into this external table, and use them to exclude or include on your analyses or campaigns. This table can be easily loaded and unloaded to include all campaigns, or just the most recent ones.
You can also load other lists in this table that can be used to exclude or include based on your needs. With the “empty” columns, you can load any data that you would like to temporarily use in your Epiphany solution. And with the attributes that are created on these columns, you can use them in your reports or campaigns.
External tables are quick and easy ways to load temporary data into your Epiphany system for analyses, or inclusion / exclusion purposes.
Hi Serguei-
Sorry for the delay in getting back to you, but I have had some hardware issues that I am trying to resolve. I hope to have them done by next week, and I will verify how we have it set up once we are back up and running, and will post it back here.
Thanks,
Mike
Hello Serguie-
Once again, I am sorry for the delay in my response. I have been on a job overseas for the past month, and just have not had the time to think about anything else. I am on my way home tomorrow, but before I left, I wanted to give you a little more information on this topic.
On our system, we created a dimension called List, and a fact table called List_Import_Fact. The List dimension had 2 fields, set_desc and set_name, and the fact table had 2 fields, occur (which was always populated with a 1) and score, which is where we loaded the actual score. We then created an attribute on both of the dimensional fields, and used them in both the layouts we used for data mining, and in transactional filters. These could then be used in lists to be included or excluded.
I guess my description was not as clear as it should have been, and the functionality was not exactly what I entered. We did use the lists all the time, and using this process, we were able to include or exclude based on the filters.
I hope this help.
Mike
Hi Mike,
Ok I got that. That’s cool. You’re basically uploading data directly into base tables. I like that !
Thanks
Serguei








Hi Mike,
I like the idea but how would you “use them to exclude or include on your analyses or campaigns” ?
We’re on 6.5 and there seems to be no way to reference these tables from the front-end objects (attributes, measures).
The only way to interact with external data is by means of external scored lists. And we use them a lot.
Thanks
Serguei